Methods and apparatus for enabling use of web content on various types of devices

ABSTRACT

A method system for interactive communication with a web site using a mobile communicator having the following functionalities: receiving, at a server, an http request from a mobile communicator being used by a user, the http request identifying a website and should the mobile communicator not support a client-side script employed by the website, causing the server to emulate the script so as to enable the user to interact with the website.

REFERENCE TO RELATED APPLICATIONS

Reference is made to U.S. Provisional Patent Application No. 60/778,434,entitled TABLE OF CONTENTS, filed Mar. 1, 2006, the disclosure of whichis hereby incorporated by reference and priority of which is herebyclaimed pursuant to 37 CFR 1.78(a) (4) and (5)(i).

REFERENCE TO COMPUTER PROGRAM LISTING APPENDIX

Computer program listing appendices are submitted herewith on onecompact disc and one duplicate compact disc. The total number of compactdiscs, including duplicates, is two. The files on the compact disc aresoftware object code and accompanying files for carrying out thefunctionalities of a preferred embodiment of the invention. Their names,dates of creation, directory locations, and sizes in bytes are:

-   -   1. setupexe.txt of Jul. 28, 2008 located in folder apndx-I and        of length 7,634,597 bytes;    -   2. proxyexe.txt of Jul. 28, 2008 located in folder apndx-I and        of length 70,259,383 bytes;    -   3. setupini.txt of Jul. 27, 2008 located in folder apndx-I and        of length 2,124 bytes.

These files are referred to herein as Appendix I. The material on thecompact discs is incorporated by reference herein.

FIELD OF THE INVENTION

The present invention relates to functionalities for enabling the use ofweb content on various types of devices.

BACKGROUND OF THE INVENTION

The following publications are believed to represent the current stateof the art:

U.S. Pat. Nos. 5,860,073; 5,909,568; 6,023,714; 6,157,935; 6,199,082;7,047,033; 7,050,603 and 7,116,765;

U.S. Patent Application Publication Nos.: 2004/0093376 and 2005/0122997;

Spyglass Prism, Concepts and Applications, Spyglass Inc., 1997, pp. 1-7;and

http://www.w3.org/protocols/HTTP/HTRO_Headers.html.

SUMMARY OF THE INVENTION

The present invention seeks to provide improved functionalities fordisplaying web content on mobile communicators. The functionalitiesdescribed hereinbelow are preferably implemented together with all orpart of the functionality described in U.S. Pat. No. 7,047,033, theentire disclosure of which is hereby incorporated by reference, and maybe implemented separately or in any suitable combination, all within thescope of the present invention.

There is thus provided in accordance with a preferred embodiment of thepresent invention a method for displaying web content on a mobilecommunicator, the method including:

arranging the web content to be readily viewable on a display screen ofthe mobile communicator, in the form of at least one mobile communicatoradapted page including a plurality of adapted information bearingregions; and

providing a plurality of navlinks on the at least one mobilecommunicator adapted page, at least some of the plurality of navlinksproviding clickable access to corresponding ones of the plurality ofadapted information bearing regions.

In accordance with a preferred embodiment of the present invention, theproviding the plurality of navlinks includes:

analyzing the information bearing regions;

based on the analyzing, distinguishing between at least some of theplurality of adapted information bearing regions;

based on the analyzing and distinguishing, labeling the at least some ofthe plurality of adapted information bearing regions; and

constructing the plurality of navlinks in accordance with the labeling.

In accordance with another preferred embodiment of the present inventionthe at least one mobile communicator adapted page includes a pluralityof sequentially arranged adapted web page screens and at least some ofthe plurality of adapted information bearing regions appear on differentones of the plurality of adapted web page screens. Preferably, theplurality of navlinks includes navlinks providing clickable access toeach of the adapted information bearing regions, each navlink providingclickable access to a corresponding one of the plurality of adaptedinformation bearing regions. Additionally or alternatively, theplurality of navlinks includes navlinks providing clickable access toless than all of the plurality of adapted information bearing regions.

In accordance with yet another preferred embodiment of the presentinvention, the plurality of navlinks includes navlinks providingclickable access to multiple ones of the plurality of adaptedinformation bearing regions. Preferably, the plurality of navlinksincludes navlinks providing clickable access to multiple ones of othernavlinks. Additionally or alternatively, the plurality of navlinksincludes a cluster of navlinks.

In accordance with still another preferred embodiment of the presentinvention, the plurality of navlinks provides clickable access to onesof the adapted information bearing regions, which are not seensimultaneously on one of the plurality of sequentially arranged adaptedweb page screens due to screen size limitations. Preferably, thenavlinks are clickable icons, which provide direct access to the adaptedinformation bearing regions. Additionally or alternatively, theplurality of navlinks include at least one of a Navbar navlink; a Searchnavlink; a Menu navlink; a Login navlink and a page categories navlink.

There is also provided in accordance with another preferred embodimentof the present invention a method for displaying web content, includinga plurality of information bearing regions, on a mobile communicator,the method including:

arranging the web content, including the plurality of informationbearing regions, to be readily viewable on a display screen of themobile communicator, in the form of at least one mobile communicatoradapted page including a plurality of adapted information bearingregions, at least some of the plurality of adapted information bearingregions having identified titles;

providing a clickable titleslink which displays the titles and providesclickable access to individual ones of the plurality of adaptedinformation bearing regions corresponding to the titles.

In accordance with a preferred embodiment of the present invention, themethod also includes providing a user operable text searchfunctionality. Preferably, the method also includes providing a useroperable link search functionality. Additionally or alternatively, thearranging the web content includes converting the web page to a treerepresentation of the Document Object Model (DOM).

In accordance with another preferred embodiment of the present inventionthe method also includes on-the-fly analysis of the web content andindicating in the tree representation of the DOM those elements whichcorrespond to the information bearing regions. Preferably, the providinga plurality of navlinks includes identifying a mobile communicator whichis requesting the web page and employing the DOM representation toprovide the at least one mobile communicator adapted page which containsthe plurality of adapted information bearing regions, corresponding tothe information bearing regions, arranged in a predetermined order.Additionally or alternatively, the predetermined order is as follows:first a logo, then a cardinal region and last a navbar.

There is further provided in accordance with yet another preferredembodiment of the present invention, a system for displaying webcontent, including information bearing regions, on mobile communicators,the system including:

a server programmed to provide the following functionality:

-   -   arranging the web content to be readily viewable on a display        screen of the mobile communicator, in the form of at least one        mobile communicator adapted page including a plurality of        adapted information bearing regions; and    -   providing a plurality of navlinks on the at least one mobile        communicator adapted page, at least some of the plurality of        navlinks providing clickable access to corresponding one of the        plurality of adapted information bearing regions.

In accordance with a preferred embodiment of the present invention theproviding the plurality of navlinks includes:

analyzing the information bearing regions;

based on the analyzing, distinguishing between at least some of theplurality of adapted information bearing regions;

based on the analyzing and distinguishing, labeling the at least ones ofthe plurality of adapted information bearing regions; and

constructing the plurality of navlinks in accordance with the labeling.

In accordance with another preferred embodiment of the present inventionthe at least one mobile communicator adapted page includes a pluralityof sequentially arranged adapted web page screens and at least some ofthe plurality of adapted information bearing regions appear on differentones of the plurality of adapted web page screens. Preferably, theplurality of navlinks includes navlinks providing clickable access toeach of the information bearing regions, each navlink providingclickable access to a corresponding one of the plurality of adaptedinformation bearing regions. Additionally or alternatively, theplurality of navlinks includes navlinks providing clickable access toless than all of the plurality of adapted information bearing regions.

In accordance with yet another preferred embodiment of the presentinvention the plurality of navlinks includes navlinks providingclickable access to multiple ones of the plurality of adaptedinformation bearing regions. Preferably, the plurality of navlinksincludes navlinks providing clickable access to multiple ones of othernavlinks. Additionally or alternatively, the plurality of navlinksincludes a cluster of navlinks.

In accordance with still another preferred embodiment of the presentinvention the plurality of navlinks provide clickable access to ones ofthe adapted information bearing regions, which are not seensimultaneously on one of the plurality of sequentially arranged adaptedweb page screens due to screen size limitations. Preferably, thenavlinks are clickable icons, which provide direct access to the adaptedinformation bearing regions. Additionally or alternatively, theplurality of navlinks include at least one of a Navbar navlink; a Searchnavlink; a Menu navlink; a Login navlink and a page categories navlink.

There is additionally provided in accordance with an additionalpreferred embodiment of the present invention a system for displayingweb content, including a plurality of information bearing regions, on amobile communicator, the system including:

a server programmed to provide the following functionality:

-   -   arranging the web content to be readily viewable on a display        screen of the mobile communicator, in the form of at least one        mobile communicator adapted page including a plurality of        adapted information bearing regions, at of at least some of the        plurality of adapted information bearing areas having identified        titles; and        -   providing a clickable titleslink which displays the titles            and provides clickable access to individual ones of the            plurality of adapted information bearing areas corresponding            to the titles.

In accordance with a preferred embodiment of the present invention thefunctionality also includes providing a user operable text searchfunctionality. Preferably, the functionality also includes providing auser operable link search functionality. Additionally or alternatively,the arranging the web content includes converting the web page to a treerepresentation of the Document Object Model (DOM).

In accordance with another preferred embodiment of the present inventionthe system also includes functionality providing on-the-fly analysis ofthe web content and indicating in the tree representation of the DOMthose elements which correspond to the information bearing regions.Preferably, the providing includes identifying a mobile communicatorwhich is requesting the web content and employing the DOM representationto provide the adapted web page which contains the plurality of adaptedinformation bearing regions corresponding to the plurality ofinformation bearing regions arranged in a predetermined order.Additionally or alternatively, the predetermined order is as follows:first a logo, then a cardinal region and last a navbar.

There is also provided in accordance with yet another preferredembodiment of the present invention a method for configuring web contentfor display on mobile communicators including:

receiving an operator-selected web page;

selection, by an operator, of at least one cell-based element of the webpage;

arrangement, by an operator, of the at least one cell-based element at adesired position in a page template; and

creating at least one mobile communicator adapted page by automaticallyplacing at least one cell-based element, indicated by the template, ofat least another web page, having a page structure similar to theoperator-selected web page, at a desired position indicated by thetemplate.

In accordance with a preferred embodiment of the present invention, theoperator initially views web sites on the Internet and thereafterarranges and prioritizes the web content thereof for viewing on mobilecommunicators. Preferably, the operator decides how given web sitesappear on display screens of the mobile communicators. Additionally oralternatively, the operator instructs a server how to arrange the webcontent displayed on display screens of the mobile communicators.

In accordance with another preferred embodiment of the presentinvention, there is displayed on a display screen of a computer of theoperator:

the operator-selected web page;

a Document Object Model (DOM);

a prioritization and arrangement table; and

a table containing the HTML code corresponding to the at least onecell-based element selected by the operator.

In accordance with yet another preferred embodiment of the presentinvention the creating employs a matching algorithm. Preferably, the atleast another web page is a future web page having at least certainstructural similarities to the operator-selected web page. Additionallyor alternatively, the at least another web page is a different web pagehaving at least certain structural similarities to the operator-selectedweb page.

In accordance with still another preferred embodiment of the presentinvention selection, arrangement and creating steps take place withoutchanging HTML code of the operator-selected web page. Additionally oralternatively, the creating includes adding additional content, withinselected elements, which was not present in the operator-selected webpage.

In accordance with a further preferred embodiment of the presentinvention the creating includes removal of web content from selectedelements when creating the template. Preferably, the operator initiallyselects the scope of a template to be created by using regularexpressions. Additionally, the operator thereafter clicks on cell-basedelements in the DOM or in the operator-selected web page in order toselect them for addition to the template.

In accordance with a yet further preferred embodiment of the presentinvention the selection includes filtering part of the content from atleast one selected cell-based element. Preferably, if there existcell-based elements template having an attribute which is likely to bedifferent at different times at which the web page is viewed, theoperator is enabled to instruct that such attribute be ignored in thecreating step. Additionally or alternatively, following the arrangement,by an operator, of the at least one cell-based element at a desiredposition in the template, the template is saved on a server.

In accordance with a still further preferred embodiment of the presentinvention information saved on the server for each cell-based element inthe template includes at least one of a priority of the cell-basedelement, its X and Y positions within the operator-selected web page,the area of the operator-selected web page taken up by the cell-basedelement, the number of images included in the cell-based element, thenumber of forms included in the cell-based element, the percentage ofthe area of the cell-based element which is covered by text and thepercentage of the area of the cell-based element which is covered bylinks and the path of the cell-based element relative to the <body> tagas it appears in the tree representation of the template DOM.Preferably, information saved on the server for each cell-based elementin the template include at least one of the following:

for cell-based elements in which the operator added or removed content,an indication that such features exist;

cell-based elements which include a basic structure which is repeatedseveral times.

In accordance with another further preferred embodiment of the presentinvention the operator may indicate whether one or more cell-basedelements in the template are mandatory elements, such that whenemploying the template to generate an adapted web page for display on amobile communicator display screen, if one of these cell-based elementsin the template is not matched by an cell-based element in the web pagebeing adapted, the template is not used. Preferably, the template iscreated for a single URL. Alternatively, the template is created for agroup of URLs defined by a regular expression.

There is further provided in accordance with a further preferredembodiment of the present invention a system for configuring web contentfor display on mobile communicators including a computer programmed toprovide the following functionalities:

receiving an operator-selected web page;

selection, by an operator, of at least one cell-based element of the webpage;

arrangement, by an operator, of the at least one cell-based element at adesired position in a page template; and

creating at least one mobile communicator adapted page by automaticallyplacing at least one cell-based element, indicated by the template, ofat least another web page, having a page structure similar to theoperator-selected web page, at a desired position indicated by thetemplate.

In accordance with a preferred embodiment of the present invention thecomputer is programmed to enable the operator initially to view websites on the Internet and thereafter arrange and prioritize the webcontent thereof for viewing on mobile communicators. Preferably, thecomputer is programmed to enable the operator to decide how given websites appear on display screens of the mobile communicators.Additionally or alternatively, the computer is programmed to enable theoperator to instruct a server how to arrange the web content displayedon display screens of the mobile communicators.

In accordance with another preferred embodiment of the present inventionthe computer is programmed such that there is displayed on a displayscreen of the computer of the operator:

the operator-selected web page;

a Document Object Model (DOM);

a prioritization and arrangement table; and

a table containing the HTML code corresponding to the at least onecell-based element selected by the operator.

In accordance with yet another preferred embodiment of the presentinvention the computer is programmed to enable the creating to employ amatching algorithm. Preferably, the at least another web page is afuture web page having at least certain structural similarities to theoperator-selected web page.

In accordance with still another preferred embodiment of the presentinvention the at least another web page is a future web page having atleast certain structural similarities to the operator-selected web page.Preferably, the computer is programmed to enable the selection,arrangement and creating steps to take place without changing HTML codeof the operator-selected web page. Additionally or alternatively, thecomputer is programmed to enable the creating to include addingadditional content, within selected elements, which was not present inthe operator-selected web page.

In accordance with a further preferred embodiment of the presentinvention the computer is programmed to enable the creating to includeremoval of web content from selected elements when creating thetemplate. Preferably, the computer is programmed to enable the operatorinitially to select the scope of a template to be created by usingregular expressions and thereafter to select an appropriate web page andviews it along with a tree representation of a Document Object Model(DOM). Additionally or alternatively, the computer is programmed toenable the operator thereafter to click on cell-based elements in theDOM or in the operator-selected web page in order to select them foraddition to the template.

In accordance with a yet further preferred embodiment of the presentinvention the computer is programmed such that if there exist cell-basedelements template having an attribute which is likely to be different atdifferent times at which the web page is viewed, the operator mayinstruct that such attribute should be ignored in the creating step.Preferably, the computer is programmed such that following thearrangement, by an operator, of the at least one cell-based element at adesired position in the template, the template is saved on a server.Additionally or alternatively, information saved on the server for eachcell-based element in the template includes at least one of a priorityof the cell-based element, its X and Y positions within theoperator-selected web page, the area of the operator-selected web pagetaken up by the cell-based element, the number of images included in thecell-based element, the number of forms included in the cell-basedelement, the percentage of the area of the cell-based element which iscovered by text and the percentage of the area of the cell-based elementwhich is covered by links and the path of the cell-based elementrelative to the <body> tag as it appears in the tree representation ofthe template DOM.

In accordance with a still further preferred embodiment of the presentinvention information saved on the server for each cell-based element inthe template include at least one of the following: for cell-basedelements in which the operator added or removed content, an indicationthat such features exist; cell-based elements which include a basicstructure which is repeated several times. Preferably, the computer isprogrammed to enable the operator to indicate whether one or morecell-based elements in the template are mandatory elements, such thatwhen employing the template to generate an adapted web page for displayon a mobile communicator display screen, if one of these cell-basedelements in the template is not matched by an cell-based element in theweb page being adapted, the template is not used. Additionally oralternatively, the template is created for a single URL. Alternatively,the template is created for a group of URLs defined by a regularexpression.

There is yet further provided in accordance with a yet further preferredembodiment of the present invention a method for displaying web contenton a device including:

requesting a web page by a user;

in response to a user request, downloading the web page to a server;

searching for at least one template for the web page on a database ofthe server;

if a template is found for the web page, effecting best matching betweenthe template and a plurality of information bearing regions on the webpage; and

importing the plurality of information bearing regions to at least onedevice adapted page.

In accordance with a preferred embodiment of the present invention thetemplate includes matching assist instructions.

There is still further provided in accordance with a still furtherpreferred embodiment of the present invention a method of obtaininginformation from at least one dynamic website, the method including:

constructing at least one template of at least a part of a web page ofthe at least one website when the web page is in a first state; and

employing the at least one template to extract information from at leastone web page of the at least one dynamic website when at least one ofthe at least one web page is in a second state, different from the firststate.

In accordance with a preferred embodiment of the present invention theat least one template is based on a document object model (DOM).Preferably, the at least one template includes at least one cell-basedelement of the web page. Additionally or alternatively, the employingthe at least one template to extract information from at least one webpage of the at least one dynamic website when at least one of the atleast one web page is in a second state, different from the first state,includes effecting best matching between the at least one template anddocument object models (DOMs) of the at least one web page in a secondstate.

There is additionally provided in accordance with an additionalpreferred embodiment of the present invention a method of obtaininginformation from at least one dynamic website, the method including:

obtaining at least one document object model (DOM) of a web page of theat least one dynamic website when the web page is in a first state; and

employing the at least one document object model (DOM) to obtaininformation from at least one web page of the at least one dynamicwebsite when at least one of the at least one web page is in a secondstate, different from the first state.

In accordance with a preferred embodiment of the present invention theemploying the at least one document object model (DOM) to extractinformation from at least one web page of the at least one dynamicwebsite when at least one of the at least one web page is in a secondstate, different from the first state, includes effecting best matchingbetween the at least one document object model (DOM) and document objectmodels (DOMs) of the at least one web page in a second state.Preferably, the method also includes maintaining login information ofusers in a database in the form of cookies and when a user againrequests the web page, the login information of the user is retrievedand a personalized web page is displayed to the user. Additionally oralternatively, the method also includes converting a web page receivedfrom the Internet into a tree representation of the DOM. andsubsequently matching the web page to a suitable template, in order togenerate an adapted web page for display on the mobile communicator.

In accordance with another preferred embodiment of the presentinvention, in order to find a template suitable for the web page, allthe templates having a scope including the requested web page are foundand a distance between the tree representation of the web page and thetree representations of each of the templates is calculated, using atree comparison algorithm. Preferably, if the distance between the treerepresentation of the web page and the tree representation of a giventemplate is below a predetermined threshold, that template is used foradapting the web page for display on a mobile communicator.

There is also provided in accordance with another preferred embodimentof the present invention a system for displaying web content on a deviceincluding a computer programmed to support at least the followingfunctionality:

requesting a web page by a user;

in response to a user request, downloading the web page to a server;

searching for at least one template for the web page on a database ofthe server;

if a template is found for the web page, effecting best matching betweenthe template and a plurality of information bearing regions on the webpage; and

importing the plurality of information bearing regions to at least onedevice adapted page.

In accordance with a preferred embodiment of the present invention thetemplate includes matching assist instructions.

There is further provided in accordance with a further preferredembodiment of the present invention a system for obtaining informationfrom at least one dynamic website, the system including a computerprogrammed to support at least the following functionality:

constructing at least one template of at least a part of a web page ofthe at least one website when the web page is in a first state; and

employing the at least one template to extract information from at leastone web page of the at least one dynamic website when at least one ofthe at least one web page is in a second state, different from the firststate.

In accordance with a preferred embodiment of the present invention theat least one template is based on a document object model (DOM).Preferably, the at least one template includes at least one cell-basedelement of the web page. Additionally or alternatively, the employingthe at least one template to extract information from at least one webpage of the at least one dynamic website when at least one of the atleast one web page is in a second state, different from the first state,includes effecting best matching between the at least one template anddocument object models (DOMs) of the at least one web page in a secondstate.

There is yet further provided in accordance with a yet further preferredembodiment of the present invention a system for obtaining informationfrom at least one dynamic website, the system including:

obtaining at least one document object model (DOM) of a web page of theat least one dynamic website when the web page is in a first state; and

employing the at least one document object model (DOM) to obtaininformation from at least one web page of the at least one dynamicwebsite when at least one of the at least one web page is in a secondstate, different from the first state.

In accordance with a preferred embodiment of the present invention theemploying the at least one document object model (DOM) to extractinformation from at least one web page of the at least one dynamicwebsite when at least one of the at least one web page is in a secondstate, different from the first state, includes effecting best matchingbetween the at least one document object model (DOM) and document objectmodels (DOMs) of the at least one web page in a second state.Preferably, the system also includes a database in which logininformation of users is maintained in the form of cookies and whereinwhen a user again requests the web page, the login information of theuser is retrieved from the database and a personalized web page isdisplayed to the user. Additionally or alternatively, the computer isoperative to convert a web page received from the Internet into a treerepresentation of the DOM. and subsequently to match the web page to asuitable template, in order to generate an adapted web page for displayon the mobile communicator.

In accordance with another preferred embodiment of the present inventionthe computer is operative, in order to find a template suitable for theweb page, to find all the templates having a scope including therequested web page and to calculate a distance between the treerepresentation of the web page and the tree representations of each ofthe templates, using a tree comparison algorithm. Preferably, if thedistance between the tree representation of the web page and the treerepresentation of a given template is below a predetermined threshold,that template is used for adapting the web page for display on a mobilecommunicator.

There is still further provided in accordance with a still furtherpreferred embodiment of the present invention a method for displayingweb content on a display screen of a mobile communicator including:

in response to a user request, downloading the web page to a server;

supplying from the server to the mobile communicator for display on adisplay screen thereof, an adapted web page corresponding to the webpage requested by the user, the adapted web page including a Find InPage link;

clicking on the Find In Page link by the user;

displaying on the display screen of the mobile communicator a Find InPage form;

entering a search string in the Find In Page form submitted by a user;and

displaying the adapted page on the display screen and designatingoccurrences of the search string therein.

In accordance with a preferred embodiment of the present invention themethod also includes adding a link next to each occurrence of the searchstring in the adapted page in order to enable the user to readilynavigate from occurrence to occurrence. Preferably, the method alsoincludes displaying a list of occurrences of the search string prior todisplaying the adapted page on the display screen and designatingoccurrences of the search string therein. Additionally or alternatively,the list of occurrences includes links to the occurrences.

In accordance with another preferred embodiment of the present inventionthe supplying includes providing an adapted web page to the mobilecommunicator, which adapted web page includes a Find In Page link.Preferably, when the user clicks on the Find In Page link, the serverreceives a corresponding request for a Find In Page form and providesthe Find In Page form to the mobile communicator. Additionally oralternatively, the Find In Page form includes radio buttons allowing theuser to select between first and second options as well as a text entryfield allowing the user to enter a search string.

In accordance with yet another preferred embodiment of the presentinvention when the user actuates one of the radio buttons, enters asearch string and submits the form to the server, this sends a requestto the server to retrieve the initially requested web page and todesignate on the corresponding adapted web page occurrences of thesearch string entered by the user. Preferably, the server is operativesequentially to:

I. reload the same web page as originally requested by the user;

II. adapt the web page for the mobile communicator, divide the adaptedpage into a series of sequential viewable adapted screens and searchthroughout the entire adapted page for occurrences of the search string;and

III. designate each such occurrence in a manner enabled by the mobilecommunicator.

In accordance with still another preferred embodiment of the presentinvention the server is also operative to:

IV. add a link alongside each occurrence which leads to the sequentialnext occurrence, wherein the link alongside the last occurrence in theadapted page leads back to the first occurrence;

V. if a ‘list results’ option is selected, add at the beginning of theadapted page a list of occurrences showing their context including linkswhich lead to each occurrence in the adapted page.

VI. if a ‘show in page’ option is selected, cause the first of theseries of sequential viewable adapted pages in which the search stringoccurs to be displayed.

There is additionally provided in accordance with an additionalpreferred embodiment of the present invention a system for displayingweb content on a display screen of a mobile communicator including aserver programmed to support the following functionality:

in response to a user request, downloading a web page to the server;

supplying from the server to the mobile communicator for display on adisplay screen thereof, an adapted web page corresponding to the webpage requested by the user, the adapted web page including a Find InPage link;

clicking on the Find In Page link by the user;

displaying on the display screen of the mobile communicator a Find InPage form;

entering a search string in the Find In Page form submitted by a user;and

displaying the adapted page on the display screen and designatingoccurrences of the search string therein.

In accordance with a preferred embodiment of the present invention thefunctionality also includes adding a link next to each occurrence of thesearch string in the adapted page in order to enable the user to readilynavigate from occurrence to occurrence. Preferably, the functionalityalso includes displaying a list of occurrences of the search stringprior to displaying the adapted page on the display screen anddesignating occurrences of the search string therein. Additionally oralternatively, the list of occurrences includes links to theoccurrences.

In accordance with another preferred embodiment of the present inventionthe supplying includes providing an adapted web page to the mobilecommunicator, which adapted web page includes a Find In Page link.Preferably, the functionality enables the user to click on the Find InPage link, and causes the server to receive a corresponding request fora Find In Page form and provide the Find In Page form to the mobilecommunicator. Additionally or alternatively, the Find In Page formincludes radio buttons allowing the user to select between first andsecond options as well as a text entry field allowing the user to entera search string.

In accordance with yet another preferred embodiment of the presentinvention the functionality enables the user to actuate one of the radiobuttons and to enter a search string and submit the form to the server,and causes the server to sends a request to the server to retrieve theinitially requested web page and to designate on the correspondingadapted web page occurrences of the search string entered by the user.Preferably, the functionality enables the server to be operativesequentially to:

I. reload the same web page as originally requested by the user;

II. adapt the web page for the mobile communicator, divide the adaptedpage into a series of sequential viewable adapted screens and searchthroughout the entire adapted page for occurrences of the search string;and

III. designate each such occurrence in a manner enabled by the mobilecommunicator.

In accordance with still another preferred embodiment of the presentinvention the functionality also enables the server to be operative to:

IV. add a link alongside each occurrence which leads to the sequentialnext occurrence, wherein the link alongside the last occurrence in theadapted page leads back to the first occurrence;

V. if a ‘list results’ option is selected, add at the beginning of theadapted page a list of occurrences showing their context including linkswhich lead to each occurrences in the adapted page; and

VI if a ‘show in page’ option is selected, cause the first of the seriesof sequential viewable adapted pages in which the search string occursto be displayed.

There is also provided in accordance with another preferred embodimentof the present invention a method for displaying web content on adisplay screen including:

requesting a web page by a user;

in response to a user request, downloading the web page to a server;

recognizing, by the server, the presence in the web page of an imagecomprised of sub-images;

combining, by the server, the sub-images into a single image;

supplying by the server the single image for display on the displayscreen.

In accordance with a preferred embodiment of the present invention atleast one of the sub-images includes non-image information and whereinthe combining preserves the non-image information outside of the singleimage. Preferably, the recognizing and combining include:

converting the web page into a modified tree representation of the DOM;

identifying the sub-images;

for each sub-image, creating a file which includes information relatedthereto and to the composite image, the information including the sourceURL and top left corner of each sub-image in addition to the width andheight dimensions of the composite image and its background color;

in the tree representation, flagging all the sub images aside from thefirst one as being invisible;

in the src field of the first sub-image, replacing the source locationthereof by the location in the server of the file, and indicating thefirst sub-image in the tree representation with a suitable indication,such that when the user scrolls down the adapted web page and reaches ascreen in which the adapted image should be displayed and the compositeimage is requested from the server, due to the change in the src fieldof the first sub image, the location of the file is provided to theserver, rather than the location of the sub-image.

In accordance with another preferred embodiment of the present inventionthe supplying includes:

in the server, defining an area having the dimensions of the compositeimage, as indicated in the file and setting the background color of thedefined area to be the background color of the image as defined in thefile;

retrieving each of the sub-images by using the URL indicated in the srcfield of its img tag; and

placing each of the sub-images in the area defined in the server at itsappropriate location based on the position of its top left corner,indicated in the file.

There is further provided in accordance with a further preferredembodiment of the present invention a system for displaying web contenton a display screen including a server programmed to have the followingfunctionality:

receiving a web page requested by a user;

recognizing the presence in the web page of a composite image comprisedof sub-images;

combining the sub-images into a single image; and

supplying the single image for display on the display screen.

In accordance with a preferred embodiment of the present invention theserver is programmed to have the following additional functionality: ifat least one of the sub-images includes non-image information, thecombining preserves the non-image information outside of the singleimage. Preferably, the recognizing and combining functionalitiesinclude:

converting the web page into a modified tree representation of the DOM;

identifying the sub-images;

for each sub-image, creating a file which includes information relatedthereto and to the composite image, the information including the sourceURL and top left corner of each sub-image in addition to the width andheight dimensions of the composite image and its background color;

in the tree representation, flagging all the sub images aside from thefirst one as being invisible;

in the src field of the first sub-image, replacing the source locationthereof by the location in the server of the file, and indicating thefirst sub-image in the tree representation with a suitable indication,such that when the user scrolls down the adapted web page and reaches ascreen in which the adapted image should be displayed and the compositeimage is requested from the server, due to the change in the src fieldof the first sub image, the location of the file is provided to theserver, rather than the location of the sub-image.

In accordance with another preferred embodiment of the present inventionthe supplying functionality includes:

in the server, defining an area having the dimensions of the compositeimage, as indicated in the file and setting the background color of thedefined area to be the background color of the image as defined in thefile;

retrieving each of the sub-images by using the URL indicated in the srcfield of its img tag; and

placing each of the sub-images in the area defined in the server at itsappropriate location based on the position of its top left corner,indicated in the file.

There is yet further provided in accordance with a yet further preferredembodiment of the present invention a method for displaying web contenton a display screen including:

in response to a user request, downloading a web page to a server;

recognizing, by the server, the presence in the web page of an image mapcontaining a plurality of links, corresponding to portions of the imagemap;

dividing by the server the image map into a plurality of sub-imagescorresponding to the portions of the image map;

associating by the server the plurality of links corresponding ones ofthe plurality of sub-images;

supplying by the server the plurality of sub-images for display on thedisplay screen.

In accordance with a preferred embodiment of the present invention thelinks are associated with specific geographical areas forming part ofthe image. Preferably, the server employs information in the image mapto extract geographical areas of the image and their corresponding linksand to prepare the geographical areas for display as individual imageson the display screen. Additionally or alternatively, the server employsinformation indicating the spatial coordinates of each of thegeographical areas from the image map to copy that geographical areainto a new image with which is associated a unique link, correspondingto the link designated by the image map.

In accordance with another preferred embodiment of the present inventionthe server converts the web page into a tree representation of the DOMof the web page and thereafter, during analysis of the web page locates<map> tags, indicating the presence of image maps and, for each <map>tag found, locates the image associated therewith. Preferably, a set oflinks, representing each of the portions of the image map, is created.

There is still further provided in accordance with a still furtherpreferred embodiment of the present invention a system for displayingweb content on a display screen including a server programmed to enablethe following functionalities:

in response to a user request, downloading a web page to the server;

recognizing, by the server, the presence in the web page of an image mapcontaining a plurality of links, corresponding to portions of the imagemap;

dividing by the server the image map into a plurality of sub-imagescorresponding to the portions of the image map;

associating by the server the plurality of links corresponding ones ofthe plurality of sub-images;

supplying by the server the plurality of sub-images for display on thedisplay screen.

In accordance with a preferred embodiment of the present invention thelinks are associated with specific geographical areas forming part ofthe image. Preferably, the server includes functionality to enable it toemploy information in the image map to extract geographical areas of theimage and their corresponding links and to prepare the geographicalareas for display as individual images on the display screen.Additionally or alternatively, the server includes functionalityenabling it to employ information indicating the spatial coordinates ofeach of the geographical areas from the image map to copy thatgeographical area into a new image with which is associated a uniquelink, corresponding to the link designated by the image map.

In accordance with another preferred embodiment of the present inventionthe server converts the web page into a tree representation of the DOMof the web page and thereafter, during analysis of the web page locates<map> tags, indicating the presence of image maps and, for each <map>tag found, locates the image associated therewith. Preferably, a set oflinks, representing each of the portions of the image map, is created.

There is additionally provided in accordance with an additionalpreferred embodiment of the present invention a method for interactivecommunication with a web site using a mobile communicator, the methodincluding:

receiving, at a server, an http request from a mobile communicator beingused by a user, the http request identifying a website; and

should the mobile communicator not support a client-side script employedby the website, causing the server to emulate the script so as to enablethe user to interact with the website.

In accordance with a preferred embodiment of the present invention themethod also includes:

retrieving a user-agent field from the http request, the user-agentfield identifying the mobile communicator being used by the user; and

ascertaining whether the mobile communicator being used by the usersupports a given computer language or script.

In accordance with another preferred embodiment of the present inventionthe method also includes employing a conventional browser of the mobilecommunicator for communicating with the server. Preferably, the methodfurther includes employing a form submit button to replace scriptelements not supported by the mobile communicator. Additionally oralternatively, the form submit button appears as a picture whichresembles the script element.

In accordance with still another preferred embodiment of the presentinvention the script is JavaScript and the server provides client-sideemulation of the JavaScript. Preferably, when a user requests an HTMLweb page from the server, the server retrieves the requested web pagefrom the internet and searches the web page for elements that requireclient-side script emulation. Additionally or alternatively, if at leastone element that requires client-side script emulation is found, thefollowing takes place on a mobile communicator adapted web pagecorresponding to the web page requested by the user:

each element respectively indicated as “one-way” or “return”, isreplaced by an input tag of a submit type (<input type=submit . . . >)having a unique name unless the mobile communicator supports use of aninput tag of an image type, in which case an input tag of an image typeis employed instead of the input tag of a submit type.

In accordance with a further preferred embodiment of the presentinvention visual appearance of the tag of a submit type preferably isset to be similar to the visual appearance of a corresponding theelement. Preferably, if the element is within an HTML form tag having anaction attribute, the value of the action attribute of the form tag isreplaced by the IP address of the server, and if the element is notwithin an HTML form tag, an HTML form tag is created around the elementand the action attribute of the form tag is set to be the IP address ofthe server. Additionally or alternatively, a look-up table is createdfor the requested web page and indexed by the unique names of the inputtags of the submit type.

In accordance with a yet further preferred embodiment of the presentinvention the look-up table contains information including at least oneof the following items:

a name of the element to which each input tag corresponds;

an ID attribute of the element;

a type characterizing the element; and

location of the element in the DOM of the web page.

In accordance with a still further preferred embodiment of the presentinvention an input tag of a “hidden” type is added to the HTML formdefined by the HTML form tag and the value of the input tag is employedto identify the look-up table. Preferably, if the element is a selectelement, corresponding to a select region, a plurality ofoption-displaying adapted pages, each containing a limited number ofoptions are prepared, each of the available options in the select regionappearing on one of the adapted option-displaying pages, each of theavailable options being a link to the server and containing a valuewhich is employed to identify the look-up table. Additionally oralternatively, when a user clicks on a select region this results insubmission of the corresponding HTML form to the server which, uponreceipt of the HTML form submission, recognizes the HTML form submissionas a request to display the general listing of options if available oralternatively a first adapted option-displaying page.

In accordance with an additional preferred embodiment of the presentinvention a user selection of an option operates as a HTTP request tothe server, which identifies the request as an emulation request andfinds the unique name of the input tag of the submit type and the lookup table and thus finds information to enable it to identify acorresponding option element on the DOM. Preferably, the option elementis found in the following manner: the server again requests the web pagefrom the internet and creates a DOM corresponding to the web page andthe information found on the look-up table is employed to locate theoption element on the DOM. Additionally or alternatively, an eventidentified by event attributes of the element is triggered by theserver, resulting in emulation of a user operating a conventional webbrowser, producing an adapted page and the information found on thelookup table is saved in an emulation list associated with the look-uptable so that retrieving the look-up table also retrieves the emulationlist.

In accordance with another preferred embodiment of the presentinvention, then a user selects an element that has submit buttonfunctionality, but is not a select region, this selection operates as aHTTP request to the server and the server identifies this request as anemulation request, server finds the unique name of the input tag of thesubmit type and the look up table and thus finds information to enableit to identify the element selected by the user. Preferably, theuser-selected element is found in the following manner: the server againrequests the web page from the Internet and creates a DOM correspondingto the web page and the information found on the look-up table isemployed to locate the element on the DOM.

There is also provided in accordance with another preferred embodimentof the present invention a system for interactive communication with aweb site using a mobile communicator including a server programmed tosupport the following functionalities:

receiving, at a server, an http request from a mobile communicator beingused by a user, the http request identifying a website; and

should the mobile communicator not support a client-side script employedby the website, causing the server to emulate the script so as to enablethe user to interact with the website.

In accordance with a preferred embodiment of the present invention thefunctionalities also include:

retrieving a user-agent field from the http request, the user-agentfield identifying the mobile communicator being used by the user; and

ascertaining whether the mobile communicator being used by the usersupports a given computer language or script.

In accordance with another preferred embodiment of the present inventionthe functionalities also include employing a conventional browser of themobile communicator for communicating with the server. Preferably, thefunctionalities also include employing a form submit button to replacescript elements not supported by the mobile communicator. Additionallyor alternatively, the form submit button appears as a picture whichresembles the script element.

In accordance with yet another preferred embodiment of the presentinvention the script is JavaScript and the server provides client-sideemulation of the JavaScript. Preferably, when a user requests an HTMLweb page from the server, the server retrieves the requested web pagefrom the internet and searches the web page for elements that requireclient-side script emulation. Additionally or alternatively, if at leastone element that requires client-side script emulation is found, thefollowing takes place on a mobile communicator adapted web pagecorresponding to the web page requested by the user:

each element respectively indicated as “one-way” or “return”, isreplaced by an input tag of a submit type (<input type=submit . . . >)having a unique name unless the mobile communicator supports use of aninput tag of an image type, in which case an input tag of an image typeis employed instead of the input tag of a submit type.

In accordance with still another preferred embodiment of the presentinvention the visual appearance of the tag of a submit type preferablyis set to be similar to the visual appearance of a corresponding theelement.

There is further provided in accordance with a further preferredembodiment of the present invention a system for interactivecommunication with a web site using a mobile communicator according toeither of claims 171 and 172 and wherein:

if the element is within an HTML form tag having an action attribute,the value of the action attribute of the form tag is replaced by the IPaddress of the server; and

if the element is not within an HTML form tag, an HTML form tag iscreated around the element and the action attribute of the form tag isset to be the IP address of the server.

In accordance with a preferred embodiment of the present invention alook-up table is created for the requested web page and indexed by theunique names of the input tags of the submit type. Preferably, thelook-up table contains information including at least one of thefollowing items:

a name of the element to which each input tag corresponds;

an ID attribute of the element;

a type characterizing the element; and

location of the element in the DOM of the web page.

In accordance with another preferred embodiment of the present inventionan input tag of a “hidden” type is added to the HTML form defined by theHTML form tag and the value of the input tag is employed to identify thelook-up table. Preferably, if the element is a select element,corresponding to a select region, a plurality of option-displayingadapted pages, each containing a limited number of options are prepared,each of the available options in the select region appearing on one ofthe adapted option-displaying pages, each of the available options beinga link to the server and containing a value which is employed toidentify the look-up table. Additionally or alternatively, when a userclicks on a select region this results in submission of thecorresponding HTML form to the server which, upon receipt of the HTMLform submission, recognizes the HTML form submission as a request todisplay the general listing of options if available or alternatively afirst adapted option-displaying page.

In accordance with yet another preferred embodiment of the presentinvention a user selection of an option operates as a HTTP request tothe server, which identifies the request as an emulation request andfinds the unique name of the input tag of the submit type and the lookup table and thus finds information to enable it to identify acorresponding option element on the DOM. Preferably, the option elementis found in the following manner: the server again requests the web pagefrom the internet and creates a DOM corresponding to the web page andthe information found on the look-up table is employed to locate theoption element on the DOM. Additionally or alternatively, an eventidentified by event attributes of the element is triggered by theserver, resulting in emulation of a user operating a conventional webbrowser, producing an adapted page and the information found on thelookup table is saved in an emulation list associated with the look-uptable so that retrieving the look-up table also retrieves the emulationlist.

In accordance with still another preferred embodiment of the presentinvention when a user selects an element that has submit buttonfunctionality, but is not a select region, this selection operates as aHTTP request to the server and the server identifies this request as anemulation request, server finds the unique name of the input tag of thesubmit type and the look up table and thus finds information to enableit to identify the element selected by the user. Preferably, theuser-selected element is found in the following manner: the server againrequests the web page from the Internet and creates a DOM correspondingto the web page and the information found on the look-up table isemployed to locate the element on the DOM.

There is yet further provided in accordance with a yet further preferredembodiment of the present invention a method for displaying web contenton a mobile communicator including:

receiving an http request from a mobile communicator being used by auser;

retrieving at least one device identifying field from the http request,the at least one device identifying field identifying the mobilecommunicator being used by the user;

searching in a device identification database for device propertiesinformation associated with the at least one field;

if the searching is successful, adapting a web page corresponding to thehttp request in accordance with the device properties information;

if the searching is not successful, conducting at least one search of atleast one external database to obtain device properties informationregarding the mobile communicator identified by the device identifyingfield from the http request;

employing information received from the search to update the deviceidentification database with properties of the mobile communicatoridentified in the at least one device identifying field and adapting theweb page corresponding to the http request in accordance with the deviceproperties information obtained by the search; and

transmitting the web page corresponding to the http request to the usermobile communicator following the adapting.

In accordance with a preferred embodiment of the present invention adevice identifying database operator can update the device identifyingdatabase and accept or reject updates to the device identificationdatabase based on information received from the search. Preferably, theat least one search includes at least one of a header search and atleast one external database searches. Additionally or alternatively, adevice identifying database operator is enabled to set a priority ofeach of a plurality of search resources available for the at least onesearch

In accordance with another preferred embodiment of the present inventionthe at least one device identifying field is a user-agent field and thedevice identifying database is a user-agent database. Preferably, thedevice identifying database is a hierarchical database.

There is still further provided in accordance with a still furtherpreferred embodiment of the present invention a system for displayingweb content on a mobile communicator including a server programmed tosupport the following functionality:

receiving an http request from a mobile communicator being used by auser;

retrieving at least one device identifying field from the http request,the at least one device identifying field identifying the mobilecommunicator being used by the user;

searching in a device identification database for device propertiesinformation associated with the at least one field;

if the searching is successful, adapting a web page corresponding to thehttp request in accordance with the device properties information;

if the searching is not successful, conducting at least one search of atleast one external database to obtain device properties informationregarding the mobile communicator identified by the device identifyingfield from the http request;

employing information received from the search to update the deviceidentification database with properties of the mobile communicatoridentified in the at least one device identifying field and adapting theweb page corresponding to the http request in accordance with the deviceproperties information obtained by the search; and

transmitting the web page corresponding to the http request to the usermobile communicator following the adapting.

In accordance with a preferred embodiment of the present invention thefunctionality enables a device identifying database operator to updatethe device identifying database and accept or reject updates to thedevice identification database based on information received from thesearch. Preferably, the at least one search includes at least one of aheader search and at least one external database searches. Additionallyor alternatively, the functionality enables a device identifyingdatabase operator is enabled to set a priority of each of a plurality ofsearch resources available for the at least one search

In accordance with another preferred embodiment of the present inventionthe at least one device identifying field is a user-agent field and thedevice identifying database is a user-agent database. Preferably, thedevice identifying database is a hierarchical database.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be understood and appreciated from thefollowing detailed description taken in conjunction with the drawings inwhich:

FIG. 1 is a simplified pictorial illustration of functionality fordisplaying web content on a mobile communicator in accordance with apreferred embodiment of the present invention, providing navlinkfunctionality in accordance with a preferred embodiment of the presentinvention;

FIG. 2A is a simplified illustration of an adapted page screen on adisplay screen of a mobile communicator showing a portion of anavigation bar of a web page accessed by using navlink functionality;

FIG. 2B is a simplified illustration of an adapted page screen on adisplay screen of a mobile communicator showing a search form of a webpage accessed by using navlink functionality;

FIG. 2C is a simplified illustration of an adapted page screen on adisplay screen of a mobile communicator showing a further menu ofnavlinks accessed by using navlink functionality;

FIG. 2D is a simplified illustration of an adapted page screen on adisplay screen of a mobile communicator showing a login form of a webpage accessed by using navlink functionality;

FIG. 2E is a simplified illustration of an adapted page screen on adisplay screen of a mobile communicator showing a list of page toptitles of a web page accessed by using navlink functionality;

FIG. 2F is a simplified illustration of an adapted page screen on adisplay screen of a mobile communicator showing a list of pagecategories of a web page accessed by using navlink functionality;

FIG. 3 is a simplified flow chart illustrating navlink functionality asillustrated in FIGS. 1-2F;

FIG. 4A is a simplified generalized flowchart illustrating functionalityfor location and display of a portion of a navigation bar of a web pageaccessed by using navlink functionality;

FIG. 4B is a simplified flowchart illustrating functionality forclassifying an HTML element as a link cluster, which functionality is astage of the functionality of FIG. 4A;

FIGS. 4C, 4D, 4E, 4F, 4G, 4H and 4I together are a simplified flowchartillustrating functionality for focusing a link cluster, whichfunctionality is another stage of the functionality of FIG. 4A;

FIGS. 4J, 4K, 4L and 4M together are a simplified flowchart illustratingfunctionality for determining the type of a link cluster, whichfunctionality is a yet another stage of the functionality of FIG. 4A;

FIGS. 4N and 4O together are a simplified flowchart illustratingfunctionality for determining whether a bottom aligned link cluster is anavbar, which functionality forms part of a final stage of thefunctionality of FIG. 4A;

FIGS. 4P, 4Q, 4R, 4S, 4T and 4U together are a simplified flowchartillustrating functionality for determining whether a top aligned linkcluster is a navbar, which functionality forms part of a final stage ofthe functionality of FIG. 4A;

FIGS. 4V, 4W, 4X, 4Y, 4Z and 4AA together are a simplified flowchartillustrating functionality for determining whether a left aligned linkcluster is a navbar, which functionality forms part of a final stage ofthe functionality of FIG. 4A;

FIGS. 4AB, 4AC, 4AD, 4AE, 4AF and 4AG together are a simplifiedflowchart illustrating functionality for determining whether a rightaligned link cluster is a navbar, which functionality forms part of afinal stage of the functionality of FIG. 4A;

FIG. 4AH is a simplified flowchart illustrating functionality fordetermining whether an HTML element is a hidden element, whichfunctionality forms part of any of the stages of the functionality ofFIG. 4A;

FIG. 5 is a simplified flow chart illustrating functionality for displayof a search region of a web page accessed by using navlinkfunctionality;

FIG. 6 is a simplified flow chart illustrating functionality for displayof a further menu of navlinks accessed by using navlink functionality;

FIG. 7 is a simplified flow chart illustrating functionality for displayof a login region of a web page accessed by using navlink functionality;

FIGS. 8A, 8B and 8C are together a simplified flow chart illustratingfunctionality for display of a list of page top titles and/or a list ofpage categories of a web page accessed by using navlink functionality;

FIGS. 9A, 9B, 9C, 9D, 9E, 9F, 9G and 9H illustrate server-side Find inPage functionality constructed and operative in accordance with apreferred embodiment of the present invention;

FIG. 10 is a simplified flow chart illustrating the Find In Pagefunctionality of FIGS. 9A-9H;

FIG. 11 is a simplified pictorial illustration of visual design tool(VDT) functionality for enabling an operator to prioritize web contentto be displayed on a mobile communicator in accordance with a preferredembodiment of the present invention;

FIG. 12 is a simplified illustration of a display screen of a mobilecommunicator showing the prioritized web content selected by theoperator in FIG. 11;

FIGS. 13 and 14 are respectively a simplified pictorial illustration ofa web page similar to that appearing in FIG. 11 and the correspondingdisplay screen of a mobile communicator, produced in accordance with theVDT functionality illustrated in FIGS. 11 and 12;

FIGS. 15 and 16 are respectively a simplified pictorial illustration ofa web page, which is different from that appearing in FIG. 11, and thecorresponding display screen of a mobile communicator;

FIG. 17 is a simplified pictorial illustration of a form enabling anoperator of the VDT functionality of FIGS. 11 to 16 to create a templatebased on a regular expression;

FIG. 18 is a simplified flow chart illustrating the operation of the VDTfunctionality illustrated in FIGS. 11-16;

FIGS. 19A and 19B are simplified pictorial illustrations of two webpages having structural similarities but significant differencestherebetween, adapted for display on a mobile communicator displayscreen in accordance with matching algorithms constructed and operativein accordance with a preferred embodiment of the present invention;

FIGS. 20A and 20B are simplified pictorial illustrations of displayscreens of mobile communicators showing the web pages of FIGS. 19A and19B as adapted for display on a mobile communicator display screen;

FIG. 21 is a simplified generalized flowchart illustrating the operationof the matching algorithm having the functionality illustrated in FIGS.19A-20B;

FIGS. 22A, 22B, 22C, 22D and 22E together are a simplified flow chart ofa first phase of the matching algorithm of FIG. 21;

FIGS. 23A, 23B, 23C, 23D, 23E, 23F and 23G together are a simplifiedflow chart of a second phase of the matching algorithm of FIG. 21;

FIGS. 24A, 24B, 24C, 24D and 24E together are a simplified flow chart ofa third phase of the matching algorithms of FIG. 21;

FIG. 25 is a simplified flow chart of a tree comparison algorithm usedduring operation of the matching algorithm of FIGS. 21-24E;

FIGS. 26A, 26B and 26C together are a simplified flow chart of a boxelement comparison algorithm used during operation of the matchingalgorithm of FIGS. 21-24E;

FIGS. 27A and 27B together are a simplified flow chart of an end elementcomparison algorithm used during operation of the matching algorithm ofFIGS. 21-24E;

FIGS. 28A, 28B, 28C, 28D and 28E together are a simplified flow chart ofa repeated structure-adapting algorithm used during operation of thematching algorithm of FIGS. 21-24E;

FIGS. 29A and 29C are simplified pictorial illustrations of a dynamicweb page, having two different structural layouts, each being associatedwith a different template in accordance with the VDT functionality ofFIGS. 11-18;

FIGS. 29B and 29D are simplified pictorial illustrations of displayscreens of mobile communicators showing the respective web pages ofFIGS. 29A and 29C as adapted for display on a mobile communicatordisplay screen, due to operation of the matching algorithm of FIGS.21-28E;

FIG. 30A is a simplified pictorial illustration of functionality forreconstruction of fragmented images for display on a mobile communicatorin accordance with a preferred embodiment of the present invention;

FIGS. 30B and 30C together are a simplified flow chart showing theoperation of the functionality for reconstruction of fragmented images;

FIG. 31 is a simplified pictorial illustration of functionality fordisplaying web content on a mobile communicator in accordance with apreferred embodiment of the present invention, providing image mapfunctionality;

FIGS. 32A, 32B 32C and 32D illustrate examples of display screens ofmobile communicators employing the image map functionality of FIG. 31;

FIG. 33 is a simplified flow chart illustrating the image mapfunctionality of FIGS. 31-32D;

FIG. 34 is a simplified pictorial illustration of functionality forclient-side script emulation in accordance with a preferred embodimentof the present invention;

FIGS. 35A, 35B and 35C together are a simplified flow chart illustratingoperation of the client-side script emulation of FIG. 34;

FIGS. 36A, 36B, 36C, 36D, 36E, 36F and 36G illustrate examples ofdisplay screens of mobile communicators employing the client-side scriptemulation functionality of FIGS. 34 and 35;

FIGS. 37A and 37B together are simplified illustrations of the structureand operation of functionality for automatic configuration of a databaseused to adapt web content for use with mobile communicators, constructedand operative in accordance with a preferred embodiment of the presentinvention; and

FIGS. 38A and 38B together are a simplified flow chart of operation ofthe functionality for automatic configuration of FIGS. 37A and 37B.

Attached herewith is the following appendix which aids in theunderstanding and appreciation of one preferred embodiment of theinvention shown and described herein:

A CD-ROM Appendix is enclosed herewith from which can be derived fileswhich taken together provide functionalities in accordance with thepreferred embodiments of the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Reference is now made to FIG. 1, which is a simplified pictorialillustration of functionality for displaying web content on a mobilecommunicator in accordance with a preferred embodiment of the presentinvention, providing navlink functionality, and to FIGS. 2A-2F, whichillustrate examples of display screens of mobile communicators employingnavlink functionality.

As seen in FIG. 1, the functionality of the present invention isoperative to display web content, such as a conventional web page 100 inthe form of adapted web content, such as an adapted web page 101, on adisplay screen 102 of a mobile communicator 104 in a manner which isparticularly suitable for viewing on display screen 102. An adapted webpage may include and typically includes a plurality of typicallyscrollable or clickable sequentially arranged adapted web page screens.This functionality and the underlying enabling technology is based onfunctionality is described in applicant/assignee's U.S. Pat. No.7,047,033, the entire disclosure of which is hereby incorporated byreference.

The functionalities described hereinbelow are preferably implementedtogether with all or part of the functionality described in U.S. Pat.No. 7,047,033 and may be implemented separately or in any suitablecombination, all within the scope of the present invention.

The functionality described in U.S. Pat. No. 7,047,033 combined with thefunctionality of this embodiment of the present invention, is preferablycarried out by a server 106 which serves as an intermediary between amultiplicity of mobile communicators 104 and web servers (not shown)such as those hosting web pages such as web page 100.

It is seen that a conventional web page, such as web page 100, has aplurality of information bearing regions. The information bearingregions may include a logo, designated by reference numeral 110; asearch region, designated by reference numeral 112; page categories, twoof which appear on web page 100 and are designated by reference numerals114 and 116; a navigation bar or navbar, designated by reference numeral122 and a page top title, designated by reference numeral 124.

The information bearing regions also include a cardinal region 126,which usually includes the main feature of the web page, such as themain story in a news web page. It is appreciated that the term cardinalregion may also be used in the art to include a mega information bearingregion, typically larger than cardinal region 126 and also includingpage categories, such as page categories 114 and 116, a page top title,such as page top title 124, and a search region, such as search region112.

It is a particular feature of the present invention that there isprovided a method and system for displaying web content, such as that ofweb page 100, on a mobile communicator, such as mobile communicator 104,including:

arranging the web content, such as that of web page 100, to be readilyviewable on display screen 102 of the mobile communicator 104, in theform of at least one mobile communicator adapted web page, such as webpage 101, including a plurality of adapted information bearing regions,corresponding to the information bearing regions appearing in web page100; and

providing a cluster 140 of navlinks 142 on the mobile communicatoradapted page 101, at least some of the cluster 140 of navlinks 142providing clickable access to corresponding at least ones of theinformation bearing regions.

The adapted information bearing regions on adapted web page 101 may beidentical to the information bearing regions on web page 100 or maycontain identical or similar information content thereto but in adifferent format.

In the illustrated embodiment, the adapted information bearing regionsinclude an adapted logo, designated by reference numeral 144,corresponding to logo 110. In accordance with a preferred embodiment ofthe present invention, the cluster 140 of navlinks 142 providesclickable access to additional adapted information bearing regions,which are not seen simultaneously on an adapted page screen of theadapted page 101 due to screen size limitations. The navlinks 142preferably are clickable icons, which provide direct access to suchinformation bearing regions.

In the illustrated embodiment, one of the navlinks 142 appears as aNavbar navlink icon 146. Clicking on this navlink causes an adaptednavbar 152, corresponding to the navigation bar or navbar 122 on webpage 100, to appear, as seen in the adapted page screen of FIG. 2A.

Another one of the navlinks 142 appears as a Search navlink icon 154.Clicking on this navlink causes an adapted search region 156,corresponding to search region 112 on web page 100, to appear, as seenin the adapted page screen of FIG. 2B.

An additional one of the navlinks 142 appears as a Menu navlink icon158. This is a different type of navlink, inasmuch as clicking on thisnavlink causes a further menu 160 of links to appear, as seen in theadapted page screen of FIG. 2C. The menu 160 of links may provide directclickable access to a login form and/or to additional adaptedinformation bearing regions such as, for example, page categories 114and 116 and page top title 124 of web page 100.

The link that provides direct clickable access to page top titles isalso termed a Titleslink. As illustrated, the menu 160 of links includesa Login link 162 and a Titleslink 163 and may also include a PageCategories link 164 and a Find in page link 165. Additionally, the menu160 may enable a user to surf to a web site home page, a portal, afavorites list and a surfing history.

Clicking on the Login link 162 causes an adapted login region 166 toappear, as seen in the adapted page screen of FIG. 2D. Clicking on theTitleslink 163 causes an adapted list of page top titles 168, eachproviding a link to the page for which it is a top title, to appear, asseen in the adapted page screen of FIG. 2E. Clicking on the link of agiven page top title causes the adapted portion of the web page, forwhich it is a page top title, to be displayed. Clicking on a PageCategories link 164 causes an adapted list of page categories 170 toappear, as seen in the adapted page screen of FIG. 2F. Preferably, eachof the page categories 170 comprises a link to the area of the pagewhere the information related to that category is detailed. Clicking onthe link of a given page category causes the adapted portion of the webpage, related this category, to be displayed. Additionally oralternatively, each of the page categories 170 comprises a link to alist of page top titles related to the category, similar in appearanceto that shown in FIG. 2E.

Preferably, providing the cluster of navlinks includes:

analyzing the plurality of information bearing regions;

based on the analyzing, distinguishing between at least some of theinformation bearing regions;

based on the analyzing and distinguishing, labeling the at least ones ofthe information bearing regions; and

constructing the cluster of navlinks in accordance with the labeling.

In accordance with a preferred embodiment of the present invention, atleast ones of the information bearing regions appear on differentadapted page screens of the at least one mobile communicator adaptedpage.

Preferably, the cluster of navlinks includes navlinks providingclickable access to each of the information bearing regions, eachnavlink providing clickable access to a corresponding one of theinformation bearing regions.

In accordance with a preferred embodiment of the present invention, thecluster of navlinks includes navlinks providing clickable access tomultiple ones of the information bearing regions. In many cases,however, the cluster of navlinks includes navlinks providing clickableaccess to less than all of the information bearing regions.

It is also a particular feature of the present invention that there isprovided a method and system for displaying web content on a mobilecommunicator including:

analyzing the plurality of information bearing areas;

arranging the web content to be readily viewable on a display screen ofthe mobile communicator, in the form of at least one mobile communicatoradapted page including a plurality of information bearing areas;

based on the analyzing, identifying titles of at least some of theplurality of information bearing areas; and

providing a clickable titleslink, which displays the titles and providesclickable access to individual ones of the information bearing regionscorresponding to the titles.

It is additionally a feature of the present invention that there isprovided a user operable text search functionality.

Reference is now made to FIG. 3, which is a simplified flow chartillustrating navlink functionality as illustrated in FIGS. 1-2F. As seenin FIG. 3, when a user requests a web page, such as web page 100, theweb page is downloaded to a server, such as server 106 (FIG. 1) andconverted to a tree representation of the Document Object Model (DOM)thereof.

The server 106 is operative on the fly to analyze the web page andindicate in the tree representation of the DOM those elementscorresponding to information bearing regions. An example of an analysisalgorithm suitable for this function is described in U.S. Pat. No.7,047,033, the disclosure of which is hereby incorporated by reference.It is appreciated that during the analysis of the web page links to theinformation bearing regions are saved in the server 106.

A web page which is adapted for each particular model of mobilecommunicator is generated using information received by the server,identifying the mobile communicator which is requesting the web page,and using the DOM representation as described hereinabove. This adaptedweb page, which corresponds to adapted web page 101 (FIG. 1) containsadapted information bearing regions corresponding to the informationbearing regions arranged in a predetermined order, preferably asfollows: the logo first, then the cardinal region and last, typicallythe navbar.

In accordance with a preferred embodiment of the present invention, acluster of navlinks, such as cluster 140 (FIGS. 1-2F) is generated,providing clickable links to selected adapted information bearingregions, such as, in the example of FIGS. 1-2B, the search region andthe Navbar region. It is appreciated that each of the navlinks formingpart of the cluster of navlinks may be found and/or generated during theadaptation of the information bearing region to which it points.

The adapted page, including the cluster of navlinks, is supplied to themobile communicator, such as mobile communicator 104.

Reference is now made to FIG. 4A, which is a generalized simplified flowchart illustrating functionality for location and display of a portionof a navigation bar of a web page accessed by using navlinkfunctionality. Operation of the functionality of FIG. 4A results in adisplay screen showing a portion of a navigation bar as illustrated inFIG. 2A.

It is appreciated that with reference to FIGS. 4A-4AH, the term ‘TotalLinks’ is defined as the total number of links contained in an entiresub-tree of a given element. The term ‘Child Links’ is defined as thenumber of links contained in nodes which are within the sub-tree of thegiven element, and at depth 1 therefrom, that is, links contained in theelement's child elements. It is appreciated that any numbers included inFIGS. 4A-4AH are included for the sake of example only, and do not limitthe scope of the invention.

As seen in FIG. 4A, as a preliminary step, the web page is convertedinto a tree representation of the DOM, and all the elements therein areenumerated using depth first percolation down the tree.

At a first stage, all clusters of links are found, and the elementscontaining the clusters are flagged in the tree representation of theDOM. At a second stage, an attempt is made to focus the link clusters byselecting one or more descendent elements thereof as link clustersinstead of the current link cluster. Subsequently, the type of each linkcluster is determined. The type of the link cluster may be a top linkcluster, a bottom link cluster, a left link cluster or a right linkcluster. Finally, the link clusters of each type are reviewed to seewhether they are navbars and if they are navbars, whether they areadapted for display.

Reference is now made to FIG. 4B, which is a simplified flowchartillustrating functionality for classifying an HTML element as a linkcluster, forming a first stage of the functionality of FIG. 4A. As seenin FIG. 4B, at a first stage, all clusters of links are found, and areflagged as such in the tree representation of the DOM. An element in thetree will be classified as a link cluster, if all the followingconditions are fulfilled:

The element is of type <td> or of type <div>;

At least a certain, predetermined, proportion of the area of theelement, typically 60% of the area of the element, includes links;

The number of links in the element is within a predetermined range; and

The number of words in the element, which are not within links and donot form parts of links, are a relatively small proportion, typically nomore than 40%, of the number of strings in the element which are withinlinks.

As seen in FIG. 4C, in order to focus the link clusters in the page, thefollowing algorithm is performed for each link cluster element in thetree representation of the DOM.

If the link cluster is a hidden element in the tree representation ofthe DOM, remove the classification of the element such that it is nolonger considered to be a link cluster. The algorithm then proceeds tofocus the next link cluster element.

If the link cluster contains an image having a non-empty UseMap tag, theprocess for this link cluster ends, and the algorithm proceeds to focusthe next link cluster.

If the number of hidden links in the link cluster is greater than apredetermined number of hidden links, typically 19, which are classifiedas hidden elements by the algorithm as described hereinbelow withreference to FIG. 4AH, the algorithm proceeds to review all the childelements of the link cluster in the tree representation of the DOM tosee whether they include hidden links.

If only one of the child elements includes hidden links, that childelement is classified as a link cluster, the classification of thecurrent element is removed such that it is no longer considered to be alink cluster, and the algorithm then proceeds to focus the next linkcluster. If more than one child element of the current link clusterincludes hidden links, the process for this link cluster ends and thealgorithm proceeds to focus the next link cluster. If the number ofhidden links in the link cluster is less than or equal to thepredetermined number of hidden links, the algorithm proceeds asdescribed in FIG. 4D.

Turning to FIG. 4D, it is seen that the algorithm then proceeds toevaluate the following condition:

1. if the pixel number of the link cluster top corner is greater thanthe pixel number representing the vertical middle of the page, and thetotal number of links in the cluster is at least a predetermined numberof links, typically three, and the link cluster has at least one childlink, then the process for this link cluster ends and the algorithmproceeds to focus the next link cluster.

If condition 1 is false, the algorithm proceeds to evaluate thefollowing condition:

2. If the number of child links of the link cluster is greater than apredetermined number of child links, typically 3; and at least apredetermined percentage, typically 80% of the child links of the linkcluster are horizontally or vertically aligned, then the process forthis link cluster ends and the algorithm proceeds to focus the next linkcluster.

If condition 2 is false, the algorithm proceeds as described in FIG. 4E.

As seen in FIG. 4E, if both of the conditions described in reference toFIG. 4D are false, the algorithm then proceeds to consider only thechild elements of the link cluster containing internal links. For eachof these child elements, the algorithm proceeds to evaluate thefollowing conditions:

1. If, for each of these child elements, all of the links contained inthe entire sub-tree of the child element are either vertically orhorizontally aligned, and the links in each the child elements arealigned in the same direction; and

2. If there is more than one child element of the link cluster elementcontaining links and the area of the child elements including linkscovers at least a predetermined percentage of the cluster area,typically 75% of the cluster area.

If both conditions 1 and 2 are true, then the process for this linkcluster ends and the algorithm proceeds to focus the next link cluster.

If condition 1 is false, the algorithm then proceeds as describedhereinbelow with reference to FIG. 4G. If condition 1 is true andcondition 2 is false, the algorithm then proceeds as in FIG. 4F.

As seen in FIG. 4F, the algorithm proceeds to evaluate the followingcondition:

1. If all the child elements of the current element are verticallyaligned, and there are one or two links placed on the page above the topmost child element of the link cluster.

If condition 1 is true, then the process for this link cluster ends andthe algorithm proceeds to focus the next link cluster.

If condition 1 is false, then the algorithm proceeds to classify all thechild elements including internal links as link clusters and theclassification of the current element is removed such that it is nolonger considered to be a link cluster. The algorithm proceeds to focusthe next link cluster.

As seen in FIG. 4G, if condition 1 described hereinabove with referenceto FIG. 4E is false, the algorithm then proceeds to evaluate thefollowing condition:

1. If the child element with the highest number of total links has atleast a predetermined number of links, typically three links, and thenumber of links of this child constitutes at least a predeterminedpercentage, typically 70%, of the number of total links of the currentlink cluster.

If condition 1 is true the algorithm proceeds to classify this childelement as a link cluster, the classification of the current element isremoved such that it is no longer considered to be a link cluster, andthe algorithm proceeds to focus the next link cluster.

If condition 1 is false, the algorithm proceeds as described in FIG. 4H.

As shown in FIG. 4H, the algorithm then proceeds to evaluate thefollowing condition:

1. If the number of total links of the child element with the highestnumber of total links constitutes at least a first predeterminedpercentage, typically 50%, of the number of total links of the currentlink cluster.

If condition 1 is false, the algorithm proceeds as described hereinbelowwith reference to FIG. 4I.

If condition 1 is true, this child element is classified as a linkcluster and the classification of the current element is removed suchthat it is no longer considered to be a link cluster. The algorithm thenproceeds to evaluate the following condition:

2. If the number of total links of the child element with the secondhighest number of total links constitutes at least a secondpredetermined percentage, typically 30%, of the number of total links ofthe current link cluster, and this child element includes at least apredetermined number of internal links, typically three internal links.

If condition 2 is true, this child element is classified as a linkcluster. The algorithm then proceeds to focus the next link clusterregardless of the value of condition 2.

As seen in FIG. 4I, if condition 1 described hereinabove with referenceto FIG. 4H is false the algorithm then proceeds to evaluate thefollowing condition:

1. If the number of total links of the child element with the highestnumber of total links constitutes at least a first predeterminedpercentage, typically 30%, of the number of total links of the currentlink cluster, and the number of total links of the child element withthe second highest number of total links is at least a predeterminednumber of links, typically three, and constitutes at least a secondpredetermined percentage, typically 30%, of the number of total links ofthe current link cluster.

If condition 1 is true, the algorithm classifies both of these childelements as link clusters and the classification of the current elementis removed such that it is no longer considered to be a link cluster.The algorithm then proceeds to focus the next link cluster regardless ofthe value of condition 1.

Reference is now made to FIGS. 4J-4M, which together are a simplifiedflowchart illustrating functionality for determining the type of a linkcluster, which functionality is a third stage of the functionality ofFIG. 4A. The type of the link cluster may be a top link cluster, abottom link cluster, a left link cluster or a bottom link cluster.

As seen in FIG. 4J, in order to determine the types of the linkclusters, the following algorithm is performed for each link clusterelement in the tree representation of the DOM.

As seen in FIG. 4J, the algorithm evaluates the following condition:

1. If the top corner of the cluster is below the vertical middle of thepage.

If condition 1 is true, the cluster is considered to be a bottomcluster.

If condition 1 is false, the algorithm evaluates the followingcondition:

2. If the width of the cluster is greater than 300 pixels, or the widthof the cluster is greater than four times the height of the cluster.

If condition 2 is true, the cluster is considered to be a top cluster.

If condition 2 is false, the algorithm evaluates the followingcondition:

3. If the number of hidden links within the cluster is greater than 25.

If condition 3 is false, the algorithm proceeds as described hereinbelowwith reference to FIG. 4L.

If condition 3 is true, the algorithm proceeds as if FIG. 4K.

As seen in FIG. 4K, the algorithm then evaluates the followingcondition:

1. If the width of the cluster is greater than the height of thecluster.

If condition 1 is true, the cluster is considered to be a top cluster.If condition 1 is false, the cluster is considered to be a verticalcluster.

For a vertical cluster, the algorithm then evaluates the followingcondition:

2. If the pixel number representing cluster left corner is less than thepixel number representing the horizontal middle of the page.

If condition 2 is true, the cluster is considered to be to be a leftcluster. If condition 2 is false, it is considered to be a rightcluster.

As seen in FIG. 4L, if condition 3 described hereinabove with referenceto FIG. 4J is false the algorithm then proceeds as follows:

As seen in FIG. 4L, a list of all the non-empty anchor type elements,that is, anchor type elements pointing to an image element or a textelement, is obtained.

The algorithm then valuates the following condition:

1. If the list contains exactly a predetermined number of links,typically three links.

If condition 1 is false, the algorithm proceeds as described hereinbelowwith reference to FIG. 4M. If condition 1 is true, the algorithm thenevaluates the following condition:

2. If the left corner of the second link is to the right of the leftcorner of the first link and the left corner of the third link is to theright of the left corner of the second link.

If condition 2 is true, the cluster is considered to be a top cluster.If condition 2 is false, the algorithm then evaluates the followingcondition:

3. If the pixel number of the left side of the left most link of thecluster is less than the pixel number representing the horizontal middleof the page.

If condition 3 is true, the cluster is considered to be a left cluster.If condition 3 is false, the cluster is considered to be a rightcluster.

As seen in FIG. 4M, the algorithm evaluates the following condition:

1. If the list of non-empty anchor type elements contains more than thepredetermined number of links defined in FIG. 4L.

If condition 1 is false, the cluster does not represent a navbar and canbe ignored. If condition 1 is true, the algorithm then evaluates thefollowing condition:

2. If the third link is located to the right of the second link, and thesecond to last link is located to the right of the third to last link.

If condition 2 is true, the cluster is considered to be a top cluster.If condition 2 is false, the algorithm then evaluates the followingcondition:

3. If the number representation of the pixel at the left most end of theleft most link is less than, a first predetermined value, typically 200.

If condition 3 is true, the cluster is considered to be a left cluster.If condition 3 is false, the algorithm then evaluates the followingcondition:

4. If the number representation of the pixel at the left most end of theleft most link is greater than a second predetermined value, typically600.

If condition 4 is true, the cluster is considered to be a right cluster.If condition 4 is false, the cluster does not represent a navbar and canbe ignored.

As mentioned hereinabove with reference to FIG. 4A, at a fourth stage,the link clusters of each type are reviewed to see whether they arenavbars.

Reference is now made to FIGS. 4N and 4O, which together are asimplified flowchart illustrating functionality for determining whethera bottom aligned link cluster is a navbar, which functionality formspart of a final stage of the functionality of FIG. 4A. As seen in FIG.4N, for bottom clusters, the following two conditions are evaluated:

1. the number of text links is greater than a first predeterminednumber, typically two; AND

-   -   the average number of characters per link is equal to or less        than a second predetermined number, typically thirty; AND    -   the number of average words per link is less than a third        predetermined number, typically 4.5; and

2. the number of image links is greater than a fourth predeterminednumber, typically two; AND

-   -   the number of image links is greater than the number of text        links.

If both of conditions 1 and 2 are false, the bottom cluster is notconsidered to be a navbar.

If either of conditions 1 or 2 are true, the following conditions areevaluated, as seen in FIG. 4O:

1. the width of the cluster is greater than the height of the cluster;

2. the distance between the bottom left side corner of the cluster andthe bottom of the page is less than a first predetermined number ofpixels, typically 250 pixels;

3. the distance between the top left side corner of the cluster and thebottom of the page is less that a second predetermined number of pixels,typically 280 pixels;

4. the tops of the second and third links in the cluster are aligned.

If all of conditions 1-4 are true, then the cluster is considered to bea navbar. If any of conditions 1-4 are false, the cluster is notconsidered to be a navbar.

Reference is now made to FIGS. 4P, 4Q, 4R, 4S, 4T and 4U, which togetherare a simplified flowchart illustrating functionality for determiningwhether a top aligned link cluster is a navbar, which functionalityforms part of a final stage of the functionality of FIG. 4A. As seen inFIG. 4P, for top clusters, the following conditions are evaluated:

1. cluster width is greater than a first predetermined number of pixels,typically 100;

2. cluster height is less than a second predetermined number of pixels,typically 110;

3. location of the cluster top end is at a pixel which is equal to orless than a first predetermined pixel number, typically 500;

4. location of the cluster left end is at a pixel which is equal to orless than a second predetermined pixel number, typically 500.

If any one of conditions 1-4 is false, the cluster is not considered tobe a navbar. If all of conditions 1-4 are true, the followingconditions, as seen in FIGS. 4P, 4Q, 4R and 4S, are evaluated:

1. the number of hidden text links is greater than a first predeterminednumber, typically 19;

2. the number of hidden image links is greater than a secondpredetermined number, typically 19;

3. the word ‘home’ appears as a single word in a text link or in animage alt field;

4. there is an image with a UseMap field including at least apredetermined number of links, typically three;

5. the number of text links is greater than a predetermined number,typically 2; AND

-   -   at least one of the links has an href attribute containing a URL        which is identical to the web page domain;

6. the number of image links is greater than a predetermined number,typically 2; AND

-   -   at least one of the links has an href attribute containing a URL        which is identical to the web page domain;

7. the number of image links is greater than a predetermined number,typically 2; AND

-   -   the number of image links is greater than the number of text        links; AND    -   at least one of the links has a src attribute including one of        the words ‘menu’ and ‘nav’; AND

at least one image link includes an href field in which the parentdirectory is the domain name, or at least two image links have identicalparent directories.

If at least one of conditions 1-7 is true, the cluster is considered tobe a top navbar, as shown in FIG. 4S. As seen in FIG. 4T, if all ofconditions 1-7 are false, the following conditions are evaluated:

1. the width of the cluster is greater than a predetermined clusterwidth upper bound, typically 450

2. the pixel number representing the top alignment of the cluster isless than a predetermined number, typically 100;

3. the cluster width is less than the predetermined cluster width upperbound; AND

-   -   the cluster width is greater than a predetermined cluster width        lower bound, typically 250; AND    -   the href attributes of all the links in the cluster start with        the same domain name or with the same directory.

If all of conditions 1-3 are false, the cluster is not considered to bea navbar.

As seen in FIG. 4U, if at least one of conditions 1-3 is true, thefollowing conditions are evaluated:

1. the number of image links is greater than the number of text links;AND

-   -   the number of image links is greater than a first predetermined        number, typically 2;    -   2. the number of text links is greater than a second        predetermined number, typically 2; AND    -   the average number of characters per link is equal to or less        than a third predetermined number, typically 21; AND    -   the average number of words per link is equal to or less than a        fourth predetermined number, typically 3.

If at least one of conditions 1-2 is true, the cluster is considered tobe a top aligned navbar. If both conditions 1 and 2 are false, thecluster is not considered to be a navbar.

Reference is now made to FIGS. 4V, 4W, 4X, 4Y, 4Z and 4AA, whichtogether are a simplified flowchart illustrating functionality fordetermining whether a left aligned link cluster is a navbar, whichfunctionality forms part of a final stage of the functionality of FIG.4A. As seen in FIG. 4V, for left clusters, the following conditions areevaluated:

1. cluster width is greater than or equal to a first predeterminednumber of pixels, typically 30;

2. cluster height is greater than or equal to a second predeterminednumber of pixels, typically 30;

3. location of the cluster top end is at a pixel which is equal to orless than a first predetermined pixel number, typically 500;

4. location of the cluster top end is at a pixel which is greater thanor equal to a second predetermined pixel number, typically 40;

5. location of the cluster left end is at a pixel which is equal to orless than a third predetermined pixel number, typically 25.

If any one of conditions 1-5 is false, the cluster is not considered tobe a navbar.

As seen in FIGS. 4W, 4X and 4Y, if all of the conditions 1-5 are true,the following conditions are evaluated:

1. the number of hidden text links is greater than a first predeterminednumber, typically 19;

2. the number of hidden image links is greater than a secondpredetermined number, typically 19;

3. the word ‘home’ appears as a single word in a text link or in animage alt field;

4. there is an image with a UseMap field including at least a thirdpredetermined number of links, typically three;

5. the number of text links is greater than a fourth predeterminednumber, typically 2; AND

-   -   at least one of the links has an href attribute containing a URL        which is identical to the web page domain;

6. the number of image links is greater than a fifth predeterminednumber, typically 2; AND

-   -   at least one of the links has an href attribute containing a URL        which is identical to the web page domain;

7. the number of image links is greater than a sixth predeterminednumber, typically 2; AND

-   -   the number of image links is greater than the number of text        links; AND    -   at least one of the links has a src attribute including one of        the words ‘menu’ and ‘nav’; AND    -   at least one image link includes an href field in which the        parent directory is the domain name, or at least two image links        have identical parent directories.

If at least one of conditions 1-7 is true, the cluster is considered tobe a left aligned navbar. If all of conditions 1-7 are false, thefollowing conditions, shown in FIGS. 4Y and 4Z, are evaluated:

1. the cluster width is greater than or equal to a predetermined clusterwidth lower bound, typically 25;

2. the cluster width is less than or equal to a predetermined clusterwidth upper bound, typically 225;

3. the cluster height is greater than or equal to a predeterminedcluster height lower bound, typically 75;

4. the cluster height is less than or equal to a predetermined clusterheight upper bound, typically 1000;

5. the area covered by the cluster is less than 2.5 times the sum of theareas of all the children of the element that include links.

If at least one of conditions 1-5 is false, the cluster is notconsidered to be a navbar.

As seen in FIG. 4AA, if all of conditions 1-5 of FIGS. 4Y and 4Z aretrue, the following conditions are evaluated:

1. the number of image links is greater than the number of text links;AND

-   -   the number of image links is greater than a first predetermined        number, typically 2;

2. the number of text links is greater than a second predeterminednumber, typically 2; AND

-   -   the average number of characters per link is equal to or less        than a third predetermined number, typically 21; AND    -   the average number of words per link is equal to or less than a        fourth predetermined number, typically 3.

If at least one of conditions 1-2 is true, the cluster is considered tobe a left aligned navbar. If both conditions 1 and 2 are false, thecluster is not considered to be a navbar.

Reference is now made to FIGS. 4AB, 4AC, 4AD, 4AE, 4AF and 4AG, whichtogether are a simplified flowchart illustrating functionality fordetermining whether a right aligned link cluster is a navbar, whichfunctionality forms part of a final stage of the functionality of FIG.4A. As seen in FIG. 4AB, for right clusters, the following conditionsare evaluated:

1. cluster width is greater than or equal to a first predeterminednumber of pixels, typically 30;

2. cluster height is greater than or equal to a second predeterminednumber of pixels, typically 30;

3. location of the cluster top end is at a pixel which is equal to orless than a first predetermined pixel number, typically 500;

4. location of the cluster top end is at a pixel which is greater thanor equal to a second predetermined pixel number, typically 40;

5. the distance between the right end of the page and the location ofthe cluster right end is equal to or less than a predetermined number,typically 25.

If any one of conditions 1-5 is false, the cluster is not considered tobe a navbar.

As seen in FIGS. 4AC, 4AD and 4AE, if all of conditions 1-5 are true,the following conditions are evaluated:

1. the number of hidden text links is greater than a first predeterminednumber, typically 19;

2. the number of hidden image links is greater than a secondpredetermined number, typically 19;

3. the word ‘home’ appears as a single word in a text link or in animage alt field;

4. there is an image with a UseMap field including at least a thirdpredetermined number of links, typically three;

5. the number of text links is greater than a fourth predeterminednumber, typically 2; AND

-   -   at least one of the links has an href attribute containing a URL        which is identical to the web page domain;

6. the number of image links is greater than a fifth predeterminednumber, typically 2; AND

-   -   at least one of the links has an href attribute containing a URL        which is identical to the web page domain;

7. the number of image links is greater than a sixth predeterminednumber, typically 2; AND

-   -   the number of image links is greater than the number of text        links; AND    -   at least one of the links has a src attribute including one of        the words ‘menu’ and ‘nav’; AND    -   at least one image link includes an href field in which the        parent directory is the domain name, or at least two image links        have identical parent directories.

If at least one of conditions 1-7 is true, the cluster is considered tobe a right aligned navbar. If all of conditions 1-7 are false, thefollowing conditions, shown in FIGS. 4AE and 4AF, are evaluated:

1. the cluster width is greater than or equal to a predetermined clusterwidth lower bound, typically 25;

2. the cluster width is less than or equal to a predetermined clusterwidth upper bound, typically 225;

3. the cluster height is greater than or equal to a predeterminedcluster height lower bound, typically 75;

4. the cluster height is less than or equal to a predetermined clusterheight upper bound, typically 1000;

5. the area covered by the cluster is less than 2.5 times the sum of theareas of all the children of the element that include links.

If at least one of conditions 1-5 is false, the cluster is notconsidered to be a navbar. As seen in FIG. 4AG, if all of conditions 1-5of FIGS. 4AE and 4AF are true, the following conditions are evaluated:

1. the number of image links is greater than the number of text links;AND

-   -   the number of image links is greater than a first predetermined        number, typically 2;

2. the number of text links is greater than a second predeterminednumber, typically 2; AND

-   -   the average number of characters per link is equal to or less        than a third predetermined number, typically 21; AND    -   the average number of words per link is equal to or less than a        fourth predetermined number, typically 3.

If at least one of conditions 1-2 is true, the cluster is considered tobe a right aligned navbar. If both conditions 1 and 2 are false, thecluster is not considered to be a navbar.

Reference is now made to FIG. 4AH, which is a simplified flowchartillustrating functionality for determining whether an HTML element is ahidden element, which functionality forms part of a fourth stage of thefunctionality of FIG. 4A.

As seen in FIG. 4AH, an element, such as a link cluster, is consideredto be a hidden element if one or more of the following conditions aretrue:

1. the direct ancestor of the element in the tree is a hidden element;

2. the visibility set to the element in the element tag parameters is‘hidden’ or ‘none’;

3. the pixel number of the left of the element is smaller than −600;

4. the element name is not of type <div> and is not of type <form>, andone of the element width and element height are equal to zero.

If all of conditions 1-4 listed above are false, the element is notconsidered to be a hidden element.

Reference is now made to FIG. 5, which is a simplified flow chartillustrating functionality for display of a search form of a web pageaccessed by using navlink functionality. Operation of the functionalityof FIG. 5 results in a display screen showing a search form of a webpage as illustrated in FIG. 2B.

As seen in FIG. 5, the following algorithm is performed for each HTMLelement of the web page until a search region is found or all HTMLelements have been checked and no search region has been found.

As seen in FIG. 5, for each HTML element found, the HTML element ischecked to see whether it is an element of the type <form>. If theelement is not of the type <form>, the algorithm proceeds to look forthe next HTML element in the web page.

If the element is of the type <form>, the element is checked to seewhether the word ‘search’ appears as text or as an image alt element,i.e. a tag of the type <img alt=“search”/> near the submit button of theform indicated by the tag <input type=submit/> or <input type=img/>.Typically, the word ‘search’ should appear within 100 characters fromthe submit button. If the word ‘search’ is found, the algorithm notesthat a search region has been found and proceeds as describedhereinbelow.

If the word ‘search’ is not found, the <form> element is checked to seewhether it contains a link to GOOGLE® near the submit button of theform, indicated by the tag <input type=submit/> or <input type=img/>.Typically, a link to GOOGLE® appearing within 100 characters or tagsfrom the submit button, is indicative of a search form. If a link toGOOGLE® is found, the algorithm notes that a search region has beenfound and proceeds as described hereinbelow.

If a link to GOOGLE® was not found in the <form> element, severaladditional checks are carried out. Initially, the form is checked to seewhether it includes at least one tag of type <input>. Next, the form ischecked to see whether it includes more than a predetermined number oftags, typically three tags, of the type <input> which are visible to theuser, i.e. more than the predetermined number of input tags which arenot of the type <input type=hidden/>. As a further stage, the input tagsin the form are checked to see whether any of them are password inputtags, that is input tags of the type <input type=password/>. Finally,input tags in the form are checked to see whether at least one of themis a submit input tag, that is an input tag of the type <inputtype=submit/> or <input type=img/>.

If the checks above show that the form does not include an input tag,includes more than the predetermined number of visible input tags,includes a password input tag or does not include a submit input tag,the form does not include a search region and the next HTML element inthe page is found. If the checks above show that the form does includeat least one input tag AND does not include more than the predeterminednumber of visible input tags AND does not include a password input tagAND does include a submit input tag, the algorithm notes that a searchregion has been found and proceeds as described hereinbelow.

If a search region is found, the search region is modified for displayon a mobile communicator of the type identified by the server, asdescribed hereinabove with reference to FIG. 3.

Reference is now made to FIG. 6, which is a simplified flow chartillustrating functionality for display of a further cluster of navlinksaccessed by using navlink functionality. Operation of the functionalityof FIG. 6 results in a display screen showing a further cluster ofnavlinks as illustrated in FIG. 2C.

As seen in FIG. 6, the web page, for which the menu of navlinks is beingcreated, is downloaded to a server, such as server 106 (FIG. 1) andconverted to a tree representation of the Document Object Model (DOM).The server then analyzes the web page to find in the tree representationof the DOM those elements corresponding to information bearing regions.Links to the information bearing regions found during the analysis aresaved by the server. Additionally, links to additional web pages, suchas history, favorites and home page, are generated. The links to theinformation bearing regions and the links to the additional web pagesare adapted for display on the mobile communicator from which the pageis requested.

Reference is now made to FIG. 7, which is a simplified flow chartillustrating functionality for display of a login form of a web pageaccessed by using navlink functionality. Operation of the functionalityof FIG. 7 results in a display screen showing a login form of a web pageas illustrated in FIG. 2D.

As seen in FIG. 7, the following algorithm is performed for each HTMLelement of the web page until a login region is found or all HTMLelements have been checked and no login region has been found.

As seen in FIG. 7, for each HTML element found, the HTML element ischecked to see whether it is an element of the type <form>. If theelement is not of the type <form>, the algorithm proceeds to look forthe next HTML element in the web page.

If the element is of the type <form>, the form is checked to see whetherit includes at least one tag of type <input>. Next, the form is checkedto see whether it includes more than a predetermined number of tags,typically three tags, of the type <input> which are visible to the user,i.e. more than the predetermined number of input tags which are not ofthe type <input type=hidden/>. As a further stage, the input tags in theform are checked to see whether any of them are password input tags,that is input tags of the type <input type=password/>. Finally, inputtags in the form are checked to see whether at least one of them is asubmit input tag, that is an input tag of the type <input type=submit/>.

If the checks above show that the form does not include an input tag,includes more than the predetermined number of visible input tags, doesnot include a password input tag or does not include a submit input tag,the form does not include a login region and the next HTML element inthe page is found. If the checks above show that the form does includeat least one input tag AND does not include more than the predeterminednumber of visible input tags AND does include a password input tag ANDdoes include a submit input tag, the algorithm notes that a login regionhas been found.

If a login region is found, the login region is modified for display ona mobile communicator of the type identified by the server, as describedhereinabove with reference to FIG. 3.

Reference is now made to FIGS. 8A-8C, which together are a simplifiedflow chart illustrating functionality for display of a list of page toptitles and/or a list of page categories of a web page accessed by usingnavlink functionality. Operation of the functionality of FIGS. 8A-8Cresults in a display screen showing a list of page top titles of a webpage as seen in FIG. 2E and/or showing a list of page categories of theweb page as seen in FIG. 2F.

The functionality of FIGS. 8A-8C includes two stages, the first of whichis illustrated in FIG. 8A, typically is performed off line and ispreferably performed once for all web pages or once for each of severaldistinguishable types of web pages. The second stage is an online stage,illustrated in FIGS. 8B and 8C, which is performed on-line at the serverfor each web page requested by a user.

As seen in FIG. 8A, during the off-line stage, a set of attribute valueswhich a header is unlikely to have is determined. The attribute valuesare saved in a server, such as server 106 (FIG. 1).

Once these attributes have been determined, three neural networks arebuilt. The first neural network is operative to receive text HTMLelements and to determine which of them are text headers. The secondneural network is operative to receive image HTML elements and todetermine which of them are image headers. The third neural network isoperative to receive HTML elements which have been determined by thefirst and second neural networks to be text or image headers, and tocategorize the received headers as page top titles or as pagecategories. Once the three neural networks are built, their parametersand structures are saved in the server. It is appreciated that textheaders and image headers are elements corresponding to outstandingareas in the web page, which are likely to be titles or other headingsof sections.

The attributes for building the first neural network may includeattributes belonging to some or all of the following groups ofattributes:

attributes pertaining to the size and shape of the text HTML element;

attributes pertaining to the text in the text HTML element;

attributes pertaining to the position of the text HTML element on thepage relative to other HTML elements thereon; and

attributes pertaining to the appearance of the text HTML elementrelative to surrounding HTML elements on the same webpage.

Examples of attributes pertaining to the size and shape of the text HTMLelement include:

binary attribute indicating whether an element includes a link;

binary attribute indicating whether an element includes a link to a pagein the same domain as the current page;

attributes indicating the height and width of link in pixels; and

attribute indicating the link width/link height ratio.

Examples of attributes pertaining to the text in the text HTML elementinclude:

binary attribute indicating if all the text in the element is in boldletters;

binary attribute indicating if all the letters in the text are capitalletters;

binary attribute indicating whether the text includes at least one wordwhich is non-numeric and does not include special characters, such as %and &;

attribute indicating a fraction of the words in the text element thatstart with a capital letter;

attribute indicating the font size

binary attribute indicating if the font size of the text element ismaximal in this page; and

attributes indicating the numbers of words and lines in the textelement.

Examples of attributes pertaining to the position of the text HTMLelement on the page relative to other HTML elements therein include:

binary attribute indicating whether there is any element above and closeto the text HTML element. Typically, an element is considered to beclose to the text HTML element if it is within a window of height 45pixels and the width of the text element;

attribute indicating the distance between the text HTML element and anHTML element below it if such an element exists; and

attribute indicating whether the text HTML element is above any HTMLinput field.

Examples of attributes pertaining to the appearance of the text HTMLelement relative to surrounding HTML elements on the web page include:

binary attribute indicating whether the background color of the textHTML element is different from the background color of the element justabove it and/or of the element just below it;

binary attribute indicating whether the font color of the text HTMLelement is different from the font color of the element just above itand/or of the element just below it;

binary attribute indicating whether the background color of the textHTML element is different from the background image of the element justabove it and/or of the element just below it; and

binary attribute indicating whether the font style of the text HTMLelement is different from the font style of the element just above itand/or of the element just below it.

The attributes for building the second neural network, which attributespertain to images, include some or all of the following:

binary attribute indicating whether the HTML image includes a link;

binary attribute indicating whether the HTML image includes a link to apage in the same domain as the current page;

attributes indicating the height and width of the HTML image in pixels;

attribute indicating the width/height ratio of the HTML image;

attribute indicating the image type; and

attribute indicating whether the HTML image element includes an altparameter.

The attributes for building the third neural network, include some orall of the following:

attribute indicating the number of words in the header;

binary attribute indicating whether all the words in the header beginwith a capital letter;

binary attribute indicating whether all the letters in the header arecapital letters;

attribute indicating the number of lines in the header;

binary attribute indicating whether the header includes a verb; and

binary attribute indicating whether the header includes one or moreconjunction words, such as ‘and’, ‘but’, ‘to’ or ‘because’.

Turning to FIG. 8B, once a user requests a web page, the server readsall the HTML elements in the page. The server then generates a list ofcandidate headers by discarding HTML elements which are unlikely to beheaders, typically because they have attribute values such as thosesaved in the server during the first step of the off-line stage.

It is appreciated that if the off-line stage is performed several timesfor different distinguishable groups of web pages, prior to reading allthe HTML elements in the page requested by the user the system mustdetermine to which group of web pages the requested page belongs, inorder to employ the appropriate neural networks during following stages.

Next, for each element in the list of candidate headers, if the elementis a text element the first neural network is used to determine whetherit is really a text header. If the element is not a text element, thatis if the element is an image element, the second neural network is usedto determine whether it is an image header.

Turning to FIG. 8C, it is seen that the third neural network is used tocategorize each of the text headers and image headers, found byemploying the first and second neural networks, as a page top title oras a page category.

Typically, the page top titles are then collected and adapted fordisplay on the mobile communicator requesting the web page, as seen inFIG. 2E, and the page categories are collected and adapted for displayon the mobile communicator as seen in FIG. 2F.

Alternatively, the server may determine which of the page top titles areassociated with each of the page categories. An importance value maythen be assigned to each of the page top titles and page categoriesfound. When adapting the page categories and page top titles fordisplay, the page categories are displayed in descending order ofimportance, followed by page top titles not associated with any pagecategory. Following each given page category, and before the display ofthe next page category, the page top titles associated with the givenpage category are displayed in descending order of importance.

As a further alternative, the page categories may be adapted for displayin descending order of importance, such that each page categorycomprises a link or is associated therewith. When a user presses a linkassociated with a page category, a list of the page top titlesassociated with that page category is displayed. The page top titles maybe displayed in descending order of importance.

Reference is now made to FIGS. 9A, 9B, 9C, 9D, 9E, 9F, 9G and 9H, whichillustrate server side Find in Page functionality constructed andoperative in accordance with a preferred embodiment of the presentinvention. In accordance with a preferred embodiment of the presentinvention, there is provided a method and system for displaying webcontent on a display screen 180 of a mobile communicator 182 includingrequesting a web page by a user; in response to a user request,downloading the web page to a server (not shown), such as server 106(FIG. 1); supplying from the server to the mobile communicator 182 fordisplay on display screen 180 thereof, an adapted web page 184corresponding to the web page requested by the user, the adapted webpage including a Find In Page link 186, as shown in FIG. 9A.

When the user clicks the Find In Page link 186 (FIG. 9A) a Find In Pageform 188 is displayed on the display screen 180 of the mobilecommunicator 182, as seen in FIG. 9B. The user enters a search string inthe Find In Page form 188, as seen in FIG. 9C, and submits the form.

As seen in FIG. 9C, since the user selected a ‘show in page’ optionprior to submitting the form, an adapted web page having the occurrencesdesignated therein is displayed on display screen 180, as seen in FIG.9D. As seen in FIG. 9D, preferably each occurrence of the search stringin the adapted web page is associated which a link 190, which, uponclicking thereon, provides display of the next occurrence of the searchstring in the adapted web page.

Alternatively, the user may select a ‘list results’ option prior toentering the search string, as shown in FIG. 9E, or following enteringthe search string, as shown in FIG. 9F. In this case, a list 192 ofoccurrences and links is presented to the user, as seen in FIG. 9G, andupon clicking on a link, an adapted web page having the occurrencedesignated therein is presented to the user, as seen in FIG. 9H. As seenin FIG. 9H, each occurrence of the search string in the adapted web pageis associated which a link 194, which, upon clicking thereon, providesdisplay of the next occurrence of the search string in the adapted webpage.

Reference is now made to FIG. 10, which is a simplified flow chartillustrating the Find In Page functionality of FIGS. 9A-9H.

Initially, the user requests a web page from the server. The serverprovides an adapted web page 184 to the mobile communicator 182 whichincludes a Find In Page link 186. When the user clicks on the Find InPage link 186, the server receives a corresponding request for Find InPage form 188 and provides the Find In Page form 188 to the mobilecommunicator 182.

The Find In Page form 182 typically includes radio buttons allowing theuser to select between options A and B, as described above, as well as atext entry field allowing the user to enter a search string.

The user actuates one of the radio buttons, enters a search string andsubmits the form to the server. Submission of the form by the user sendsa request to the server to retrieve the initially requested web page andto designate on the corresponding adapted web page occurrences of thesearch string entered by the user.

This is achieved by the following steps taken by the server:

I. The server reloads the same web page as originally requested by theuser;

II. The server adapts the page for the mobile communicator 182 anddivides the adapted page into a series of sequential viewable adaptedscreens and searches throughout the entire adapted page for occurrencesof the search string.

III. The server designates each such occurrence in a manner enabled bythe mobile communicator 182.

IV. The server preferably adds a link alongside each occurrence whichleads to the sequential next occurrence. The link alongside the lastoccurrence in the adapted page leads back to the first occurrence. Theselinks are preferably directed to string token instances.

V. If the ‘list results’ option is selected, the server adds at thebeginning of the adapted page a list of occurrences showing theircontext including links which lead to each occurrences in the adaptedpage.

VI. If the ‘show in page’ option is selected, server causes the first ofthe series of sequential viewable adapted pages in which the searchstring occurs to be displayed.

Reference is now made to FIG. 11, which is a simplified pictorialillustration of visual design tool (VDT) functionality for enabling anoperator to prioritize web content to be displayed on a mobilecommunicator in accordance with a preferred embodiment of the presentinvention and to FIG. 12, which is a simplified illustration of adisplay screen of a mobile communicator showing the prioritized webcontent selected by the operator.

As seen in FIG. 11, an operator, typically an employee of a cellulartelephone company or content provider, using a computer 200, views websites on the Internet and arranges and prioritizes the web contentthereof for viewing on mobile communicators typically used by customersof his company. It may be understood that the operator decides how givenweb sites appear on display screens of mobile communicators, such asdisplay screens 102 of mobile communicators 104 (FIG. 1), whichcommunicate with a server 201, such as server 106 (FIG. 1). The operatorinstructs the server how to arrange the web content displayed on thedisplay screens of the mobile communicators.

In the illustrated embodiment of FIG. 11, an operator-selected web page202, such as an internal CNN web page, appears on the screen of theoperator's computer 200. Alongside the web page 202 appears a modifiedtree representation of the Document Object Model (DOM) 204. Typically atthe lower, left corner of the screen of the operator's computer 200,there appears a prioritization and arrangement table 206, alongside ofwhich appears a text box 208 containing the HTML code corresponding tooperator-selected information bearing regions listed in table 206.

In accordance with a preferred embodiment of the present invention,there is provided by the VDT functionality of the present invention amethod and system for displaying web content on a mobile communicatorincluding:

1. Receiving a web page, such as web page 202, by an operator;

2. Selection by the operator, typically using computer 200, of at leastone cell-based element of the web page 202. Typical cell-based elementsinclude an image of the CNN logo, designated by reference numeral 210,an image of the name of the CNN internal web page, designated byreference numeral 212 and a page top title, designated by referencenumeral 214. These cell-based elements are designated in the DOM 204respectively as IMG 220, DIV 222 and DIV 224. In the designation field,the operator may designate a selected element as a specific type ofinformation bearing region, such as a logo, a page top title or a pagecategory.

3. Arrangement by an operator of the at least one cell-based element ata desired position in a page template. In the illustrated embodiment,the order of the cell-based elements is as follows, as seen in table206: IMG 220, DIV 222 and DIV 224.

4. Creating at least one mobile communicator adapted page byautomatically placing at least one cell-based element, indicated by thetemplate, of at least another web page, having a page structure similarto that of the web page, at a desired position indicated by thetemplate. This step employs a matching algorithm, preferably analgorithm that is described hereinbelow.

It is appreciated that the “another web page” may be a future web pageand/or a different web page having at least certain structuralsimilarities to the web page which is viewed by the operator.

Preferably, the selection, arrangement and creating steps take placewithout changing HTML code of the web page.

The creating step preferably includes adding additional content, withinselected elements, which was not present in the web page. Alternatively,the operator may indicate that content should be removed from selectedelements when creating the template.

When the template includes portions having a basic structure which isrepeated several times, an addition of content or a removal of contentin the basic structure may be indicated for only one instance of thebasic structure, and an indication may be made that this addition orremoval should be carried out for each of the repetitions of the basicstructure when adapting a web page based on the template.

FIG. 12 illustrates a display screen 230 of a mobile communicator 232showing the prioritized web content selected by the operator. It is seenthat nearest to the top of the screen 230 appears an image 234 of theCNN logo corresponding to an image of the CNN logo 210 and IMG 220,given top priority by the operator, followed by an image 236 of a pagecategory, corresponding to an image of a page category 212 and DIV 222,given a second priority by the operator and followed by a page top title238, corresponding to a page top title 214 and DIV 224, given a thirdpriority by the operator.

Reference is now made to FIG. 13, which illustrates another web page240, having a page structure similar to that of the web page appearingin FIG. 11 and to FIG. 14, which illustrates a corresponding mobilecommunicator display. It is seen that the page category 246 is differentfrom page category 212 (FIG. 11) and corresponding page category 236(FIG. 12). Additionally, the page top title 248 is different from pagetop title 214 (FIG. 11) and corresponding page top title 238 (FIG. 12).The VDT functionality is operative, notwithstanding this difference, andeven notwithstanding more significant differences in the arrangement ofthe web pages, to identify and place the page category 246 and the pagetop title 248 in their proper locations on the display screen 250 of amobile communicator 252, as seen in FIG. 14 as adapted page category 256and adapted page top title 258.

Reference is now made to FIG. 15, which illustrates another web page260, which is reached via the CNN.com webpage but has a completelydifferent page structure than that of the web page appearing in FIG. 11,and to FIG. 16, which illustrates a corresponding mobile communicatordisplay. It is seen that due to the fact that the page structure of webpage 260 is so different from that of the web page appearing in FIG. 11,the VDT functionality does not recognize the web page 260 as conformingto the template defined for the web page of FIG. 11, and the web page260 is displayed on the display screen 262 of a mobile communicator 264in accordance with the automatic display functionality describedhereinabove with reference to U.S. Pat. No. 7,047,033 and FIGS. 1-8C. Asseen in FIG. 16, the adapted web page displayed on display screen 262includes a group of navlinks 266, an adapted logo 268 and an adaptedlist of page top titles 270 corresponding respectively to logo 278 andthe page top titles 280 in web page 260.

Reference is now made to FIG. 17, which is a simplified pictorialillustration of a form enabling an operator of the VDT functionality ofFIGS. 11 to 16 to create a template based on a regular expression 282and to include therein web pages not covered by that regular expression.

Reference is now made to FIG. 18, which is a simplified flow chartillustrating operation of the VDT functionality described hereinabovewith reference to FIGS. 11 to 17. As seen in FIG. 18, the operatorinitially selects the scope of a template to be created by using regularexpressions. For example, if the operator wishes to create a templateintended to cover multiple web pages having similar structures, such as,for example,

www.cnn.com/2007/news/us . . .

www.cnn.com/2007/news/world . . .

www.cnn.com/2007/news/politics . . .

the operator would use the regular expression: www.cnn.com/2007/news/*

If the operator wishes to create a template intended to cover anotherweb page, having a different structure, such as, for example,www.cnn.com/2007/sports . . . , the operator typically uses the regularexpression: www.cnn.com/2007/sports/*.

The operator then selects an appropriate web page and views it oncomputer 200 alongside a tree representation of the Document ObjectModel (DOM) 204. The operator then clicks on cell elements in the DOM204 or in the page in order to select them for addition to the templatebeing created.

Typically, the elements will be displayed on a mobile communicatordisplay screen in the order in which they were added to the template.Optionally, the operator may change the priority of some or all of theelements added to the template. In this case, the elements will bedisplayed on a mobile communicator display screen in descending order ofpriority.

Optionally, the operator may add to the template, within elementsselected from the original web page, additional content which was notpresent in the web page. The additional content provided in the templatewill be added to any adapted web page created using the template. Inthis case, the content, and the location of the node in the treerepresentation of the template, following which the content should beadded, will be saved on the server.

As a further option, the operator may remove from the template contentwhich is contained within elements selected from the original web page.The removed content indicated in the template will be removed from anyadapted web page created using the template. In this case, the content,and the location, in the tree representation of the template, of thecontent to be removed, is saved on the server.

If the web page from which the template is created includes portionshaving a basic structure which is repeated several times, an addition ofcontent or a removal of content may be indicated for only one instanceof the basic structure, and an indication may be made that this additionor removal should be carried out for each of the repetitions of thebasic structure when adapting a web page based on the template.

Any other suitable content may be added to the template by the operator.

It is appreciated that for elements in the template having an attributewhich is likely to be different at different times at which the web pageis viewed, the operator may indicate to a server that this specificattribute should be ignored when matching a given page to the template,as described hereinbelow. Such indications may be considered as “hints”for ignoring certain attributes of an element in the template.

Once the operator has added all the desired elements to the template,the template is saved on a server, such as server 201 (FIG. 11).Preferably, the information saved on the server for each element in thetemplate includes some or all of the priority of the element, its X andY positions within the web page, the area of the web page taken up bythe element, the number of images included in the element, the number offorms included in the element, the percentage of the area of the elementwhich is covered by text and the percentage of the area of the elementwhich is covered by links and the path of the element relative to the<body> tag as it appears in the tree representation of the template DOM.Preferably, the template also includes a tree representation of the webpage from which the template was created.

In this context, the path of the element is defined as a sequence ofnumbers indicating the location of an element within a treerepresentation of a DOM relative to a given root node. Starting with aroot node, the first number in the element path represents the ordinalnumber of the child element that should be selected when traversing thetree to find the element, the second number represents the ordinalnumber of the child element relative to the previous child element thatshould be selected and so forth, such that the last number locates theelement. In accordance with this definition, the length of the elementpath corresponds to the depth of the element relative to the given rootnode.

For elements in which the operator added or removed content, theinformation for the element includes an indication that content wasadded or removed. Additionally, elements are specifically indicated inthe template if such elements include a basic structure which isrepeated several times.

It is further appreciated that the operator may indicate whether one ormore elements in the template are mandatory elements. If elements areconsidered to be mandatory and they are not matched by an element in theweb page being adapted, the template is not used and the web page isdisplayed on the mobile communicator display screen as describedhereinabove with reference to FIGS. 1-8C.

Once all this information is saved on the server, the template iscreated, and may be employed in creating the page as seen on the displayscreen of the mobile communicator for both present and future,structurally similar web pages. It is appreciated that a template may becreated separately for each URL, or alternatively may be created oncefor a group of URLs defined by a regular expression.

Reference is now made to FIGS. 19A, 19B, 20A and 20B, which illustratethe results of operation of a matching algorithm, preferably, but notnecessarily, within the context of the VDT functionality.

FIGS. 19A and 19B show two web pages, respectively designated byreference numerals 300 and 302, having structural similarities butsignificant differences between them. It is seen that in both web pages300 and 302, the CNN logo remains generally in the same place. Incontrast to the foregoing, the navbar 304 of web page 300 appears at theleft portion of the page 300, while the navbar 306 in web page 302appears at the top of the web page. Additionally, the page top title 308in web page 300 appears in the lower center portion of the page 300,while the page top title 310 in web page 302 appears at the middle ofthe left most portion of the web page. Notwithstanding thesedifferences, the matching algorithm of the present invention isoperative to identify both page top titles 308 and 310 as page toptitles for the purpose of creation of web pages for mobilecommunicators.

As seen in FIGS. 19A and 19B, users request respective web pages 300 and302 from mobile communicators, respectively designated by referencenumerals 312 and 314. The requests are provided to a server 316, whichis operative to adapt the requested web pages 300 and 302 for display onthe mobile communicators 312 and 314.

FIGS. 20A and 20B show two adapted web pages, respectively designated byreference numerals 320 and 322, appearing on corresponding displayscreens 324 and 326 of respective mobile communicators 328 and 330.These web pages correspond respectively to web pages 300 and 302 shownin FIGS. 19A and 19B, respectively. It is seen that notwithstanding thedifference in position of the page top titles 308 and 310 in web pages300 and 302 respectively, the corresponding page top titles 338 and 340on web pages 320 and 322 are both located in their correctly prioritizedlocations.

In accordance with a preferred embodiment of the present invention,there is provided a method and system for displaying web content on amobile communicator enabling the following functionality:

requesting a web page by a user;

in response to a user request, downloading the web page to a server;

searching for at least one template for the web page on a database ofthe server;

if a template is found for the web page, effecting best matching betweenthe template and a plurality of information bearing regions on the webpage; and

importing the plurality of information bearing regions to at least onemobile communicator adapted page.

Preferably, the template includes matching assist instructions.

Reference is now made to FIG. 21, which is a generalized flowchartillustrating the operation of the matching algorithms having thefunctionality illustrated in FIGS. 19A to 20B.

It is appreciated that the following terms will have the definitionsprovided herein below throughout the description of the matchingalgorithm, and generally throughout the specification and claims.

‘element’—an HTML tag, or a node representing this tag in the treerepresentation of the DOM;

‘element name’—the name of an HTML tag associated with an element;

‘box element’—an HTML element of one of the following types: <body>,<table>, <tr>, <th>, <td>, <div>, <form> and <span>;

‘end element’—any HTML element which is not a box element;

‘boxed tree’—a tree representation of the DOM in which only box elementsare considered;

‘element path’—a sequence of numbers indicating the location of anelement within a tree representation of a DOM relative to a given rootnode. Starting with the root node, the first number in the element pathrepresents the ordinal number of the child element that should beselected when traversing the tree to find the element, the second numberrepresents the ordinal number of the child element relative to theprevious element that should be selected and so forth, such that thelast number locates the element. In accordance with this definition, thelength of the element path corresponds to the depth of the elementrelative to the given root node;

‘element closest box’—the closest box element to an element. For boxelements, this is the element itself. For end elements, the closest boxelement is the box element relative to which the end element has thelowest depth;

‘full tree traversal mode’—traversal of the tree representation of theDOM from root to leaves in which all the elements are considered.

‘boxed tree traversal mode’—traversal of the tree representation of theDOM from root to leaves in which only box elements are considered, andend elements are ignored. The end elements are also ignored in thedefinition of the element path for the boxed tree.

Turning now to FIG. 21, it is seen that a user requests a web page via aserver, such as server 201 (FIG. 11). The web page is downloaded via theInternet to the server and converted by the server to a treerepresentation of the DOM. The server retrieves from a VDT record in aVDT database a template corresponding to the requested web page.

A matching algorithm, described in more detail hereinbelow withreference to FIGS. 22A-24E, is used to select cell elements in therequested web page that best match corresponding cell elements in thetemplate. The cell elements of the web page found by the matchingelement are then arranged by the server as an adapted web page, inaccordance with the priority indicated by the template. If so indicatedin the template, content is added to or removed from the elements, orrepetitive structures are used for adapting the elements. The adaptedweb page is then transmitted by the server to the user.

Reference is now made to FIGS. 22A-24E, which are detailed flow chartsof three phases of the matching algorithm of FIG. 21. FIGS. 22A, 22B,22C, 22D and 22E together are a simplified flow chart of a first phaseof the matching algorithm, in which elements are matched based on theirelement path. FIGS. 23A, 23B, 23C, 23D, 23E, 23F and 23G together are asimplified flow chart of a second phase of the matching algorithm, whichis reached if the first phase was unsuccessful, and in which elementsare matched based on a search of elements surrounding the element foundby following the element path. FIGS. 24A, 24B, 24C, 24D and 24E togetherare a simplified flow chart of a third phase of the matching algorithm,which is reached if the second phase was unsuccessful, in which elementsare matched by searching the entire tree representation of the DOM.

Generally, each element in the web page is matched to an element in thetemplate by selecting an element, locating the element closest boxthereof, and matching thereto a box element from the web page. Once theelement closest boxes are matched, the algorithm proceeds to match theelement of the template to an element within the matched box element ofthe web page.

Turning specifically to FIG. 22A, it is seen that at a first stage, atree comparison algorithm, described in detail hereinbelow withreference to FIG. 25, is employed to calculate the distance between thetree representation of the web page and the tree representation of thetemplate. If the calculated distance is above a first predeterminedthreshold, typically 0.1, the matching algorithm proceeds to the secondphase thereof, which is described hereinbelow with reference to FIGS.23A-23G.

If the calculated distance is below the first threshold, the algorithmis iteratively carried out for each element in the template. Initially,the boxed tree traversal mode is employed. The element path to theselected element closest box in the template is used in order to locatea candidate matching element closest box in the tree representation ofthe web page. If, during the process of descending the tree in search ofthe candidate matching element closest box, a box element in the treerepresentation of the web page has fewer children than the respectivenumber in the element path, the matching algorithm proceeds to thesecond phase thereof, which is described hereinbelow with reference toFIGS. 23A-23G. Otherwise, a candidate matching element closest box isfound.

Turning now to FIG. 22B, it is seen that if, in the template, theinformation related to the selected element closest box includesinformation regarding ignoring all the element characteristics asidefrom the element name and its location in the tree, the name of theselected element closest box and of the candidate matching elementclosest box are compared. If the two names are identical, the matchingelement closest box has been found. Otherwise, there is no matchingelement for the selected element. In this case, if the selected elementis indicated by the operator to be a mandatory element the matchingalgorithm terminates and the page is displayed in order without use ofthe VDT template. If the selected element is not a mandatory one, anattempt is made to match the next element.

If, in the template, no information was provided regarding ignoringelement characteristics, or if the template includes an indication toignore only some of the element characteristics, the distance betweenthe candidate matching element closest box and the selected elementclosest box is calculated using a box element comparison algorithm,described hereinbelow with reference to FIG. 26. If the calculateddistance is above a second predetermined threshold, typically 0.2, thematching algorithm proceeds to the second phase thereof, which isdescribed hereinbelow with reference to FIGS. 23A-23G. Otherwise, thematching element closest box was found.

As seen in FIG. 22C, once the matching element closest box is found, thealgorithm checks whether the selected element is a box element. If theselected element is a box element, the matching element is the matchingelement closest box found in the previous stage. If the selected elementis not a box element, the algorithm matches the selected element with anend element within the matching element closest box, as describedfurther hereinbelow.

Once a matching box element is found in the tree representation of theweb page, the selected box element in the template is checked to seewhether it includes an indication of added or removed content therein orof use of an instance of a basic structure repeated therein.

If the selected box element includes an indication that content shouldbe added, the required content is found in the template, and the contentis added following the node whose location is designated in thetemplate.

As seen in FIG. 22D, if the selected box element includes an indicationthat content should be removed therefrom, the required content is foundin the template, and the content is removed from the location designatedin the template.

If the selected box element includes an indication of use of an instanceof a basic structure repeated therein for adapting other instances ofthe repeated structure, a repeated structure adapting algorithm,described hereinbelow with reference to FIGS. 28A-28E, is employed.

Returning to FIG. 22C, if, as mentioned above, the selected element isnot a box element, the algorithm matches the selected element with anend element within the matching element closest box. In order match endelements, full tree traversal mode is employed. Using an element path ofthe selected element relative to its closest box element, a candidatematching element is located within the matching closest box element.

As seen in FIG. 22D, if, during the process of descending the sub treeof the matching element closest box in search of the candidate matchingelement, an element in the tree representation of the web page has fewerchildren than the respective number in the element path, the matchingalgorithm proceeds as described further hereinbelow with reference toFIG. 22E.

As seen in FIG. 22D, if, during the process of descending the sub treeof the matching element closest box in search of the candidate matchingelement, no element in the tree representation of the web page has fewerchildren than the respective number in the element path, the candidatematching element is found and the distance between the candidatematching element and the selected element is calculated using an endelement comparison algorithm, described hereinbelow with reference toFIGS. 27A and 27B.

As seen in FIG. 22E, if the calculated distance is below a thirdpredetermined threshold, the matching element is found, and thealgorithm proceeds to match the next element.

If the calculated distance is above the third predetermined threshold,or alternatively, as described hereinabove, if during the process ofdescending the sub tree of the matching element closest box in search ofthe candidate matching element, an element in the tree representation ofthe web page has fewer children than the respective number in theelement path, the algorithm finds the minimum of the distances betweenthe selected end element and any element within the sub-tree of thematching element closest box having the same name as the selectedelement.

The distances are calculated using the end element comparison algorithm,described hereinbelow with reference to FIGS. 27A and 27B. If theminimum distance is below the third predetermined threshold, thematching element is found, and the algorithm proceeds to match the nextelement. If the minimum distance is not below the third predeterminedthreshold, the matching algorithm proceeds to the second phase thereof,which is described hereinbelow with reference to FIGS. 23A-23G.

Reference is now made to FIGS. 23A, 23B, 23C, 23D, 23E, 23F and 23G,which together are a simplified flow chart of a second phase of thematching algorithm, which is reached if the first phase wasunsuccessful, and in which elements are matched based on a search ofelements surrounding the element found based on the element path.

As seen in FIG. 23A, this phase of the matching algorithm starts byemploying boxed tree traversal mode. The distance between the firstelement named <body> in the tree representation of the template and thefirst element named <body> in the tree representation of the web page iscalculated, using the box element comparison algorithm, describedhereinbelow with reference to FIGS. 26A-26C. If the calculated distanceis above a first predetermined threshold, the matching algorithmproceeds to the third phase thereof, which is described hereinbelow withreference to FIGS. 24A-24E.

If the calculated distance is below the first predetermined threshold,the element path of the selected element closest box is retrieved, andan index is defined and set to 0. The index indicates the location ofthe algorithm within the element path, and accessing the index providesthe character located at the indicated location in the element path. Thefollowing stages are performed in a loop.

The index is incremented. If the index, exceeds the number of charactersin the element path, the matching element closest box is found and isthe box element found by following the element path in the treerepresentation of the web page. The algorithm then proceeds as describedhereinbelow with reference to FIG. 23D.

If the index does not exceed the number of characters in the elementpath, the number of the child node, as indicated by the character of theelement path to which the index is currently directed, is retrieved.Next, as seen in FIG. 23B, if the current element in the treerepresentation of the web page has a child node of the number retrievedfrom the element path, the box element having the number indicated bythe element path is retrieved from the tree representation of thetemplate and from the tree representation of the web page. The distancebetween the retrieved template box element and web page box element iscalculated using the box element comparison algorithm, describedhereinbelow with reference to FIGS. 26A-26C. If the calculated distanceis below a second predetermined threshold, the index is incremented andthe loop repeats itself for the next index.

If the calculated distance is above the second predetermined threshold,or alternatively if the child number retrieved from the element path isgreater than the number of children nodes of the element in the treerepresentation of the web page, a more complete search is conducted inthe tree representation of the web page. In this search, the distance ofthe element in the template tree located at the current location in thepath from each of the elements which are at the same depth of the treeas the current element, and which share the same immediate root node(sibling nodes of the element) is calculated.

Additionally, as seen in FIG. 23C, the distance of the element in thetemplate tree located at the current location in the path from each ofthe elements in a sub-tree of the current element which are within apredetermined depth therefrom, typically depth 2, is calculated. Theminimum distance of all the distances is found, and if it is lower thanthe second predetermined threshold, the index is incremented and theloop repeats itself for the next index. Otherwise, the matchingalgorithm proceeds to the third phase thereof, which is describedhereinbelow with reference to FIG. 24A-24E. Once the loop terminates,the matching element closest box is found.

As seen in FIG. 23D, once the matching element closest box is found, thealgorithm checks whether the selected element is a box element. If theselected element is a box element, the matching element is the matchingelement closest box found in the previous stage. If the selected elementis not a box element, the algorithm matches the selected element with anend element within the matching element closest box, as describedhereinbelow with reference to FIGS. 23F and 23G.

Once a matching box element is found in the tree representation of theweb page, the selected box element in the template is checked to seewhether it includes an indication of added or removed content therein,or of use of an instance of a basic structure repeated therein foradapting other instances of the repeated structure.

If the selected box element includes an indication that content shouldbe added, the required content is found in the template, and the contentis added following the node whose location is designated in thetemplate.

As seen in FIG. 23E, if the selected box element includes an indicationthat content should be removed therefrom, the required content is foundin the template, and the content is removed from the location designatedin the template.

If the selected box element includes an indication of use of an instanceof a basic structure repeated therein for adapting other instances ofthe repeated structure, a repeated structure adapting algorithm,described hereinbelow with reference to FIGS. 28A-28E, is employed.

As mentioned hereinabove with reference to FIG. 23D, if the selectedelement is not a box element, the algorithm matches the selected elementwith an end element within the matching element closest box. As seen inFIG. 23F, in order to match end elements, full tree traversal mode isemployed. Using an element path of the selected element relative to itsclosest box element, a candidate matching element is located within thematching element closest box.

As seen in FIG. 23F, if, during the process of descending the sub treeof the matching closest box element in search of the candidate matchingelement, an element in the tree representation of the web page has fewerchildren than the respective number in the element path, the matchingalgorithm proceeds as described further hereinbelow.

As seen in FIG. 23F, if, during the process of descending the sub treeof the matching closest box element in search of the candidate matchingelement, no element in the tree representation of the web page has fewerchildren than the respective number in the element path, the candidatematching element is found, and the distance between the candidatematching element and the selected element is calculated using an endelement comparison algorithm, described hereinbelow with reference toFIGS. 27A and 27B. If the calculated distance is below a thirdpredetermined threshold, the matching element is found, and thealgorithm proceeds to match the next element.

If the calculated distance is above the third threshold, oralternatively, as described hereinabove, if during the process ofdescending the sub tree of the matching closest box element in search ofthe candidate matching element, an element in the tree representation ofthe web page has fewer children than the respective number in theelement path, the algorithm finds the minimum of the distances betweenthe selected end element and any element within the sub-tree of thematching closest element box having the same name as the selectedelement. The distances are calculated using the end element comparisonalgorithm, described hereinbelow with reference to FIGS. 27A and 27B.

As seen in FIG. 23G, if the minimum distance is below the thirdpredetermined threshold, the matching element is found, and thealgorithm proceeds to match the next element. If the minimum distance isnot below the third predetermined threshold, the matching algorithmproceeds to the third phase thereof, which is described hereinbelow withreference to FIG. 24A-24E.

Reference is now made to FIGS. 24A, 24B, 24C, 24D and 24E, whichtogether are a simplified flow chart of a third phase of the matchingalgorithm, which is reached if the second phase was unsuccessful, and inwhich elements are matched by searching the entire tree representationof the DOM.

As seen in FIG. 24A, this phase of the matching algorithm starts byemploying boxed tree traversal mode. In order to find a candidatematching element closest box, the distance between each of the boxelements in the tree representation of the DOM and the selected elementclosest box is calculated, using the box element comparison algorithm,described hereinbelow with reference to FIGS. 26A-26C. The elementhaving the minimum of all the distances is found, and is considered tobe the candidate matching element closest box. If the minimum distanceis lower than a predetermined threshold, the matching element closestbox is found and the algorithm proceeds as described furtherhereinbelow.

If the minimum distance is not lower than a first predeterminedthreshold, there is no matching element for the selected element. If theselected element is indicated by the operator to be a mandatory elementthe matching algorithm terminates and the page is displayed in orderwithout use of the VDT template. If the selected element is notmandatory, the algorithm proceeds to process the next element.

As described hereinabove, if the minimum distance is lower than a firstpredetermined threshold, the matching element closest box is found andthe algorithm checks whether the selected element is a box element. Ifthe selected element is a box element, the matching element is thematching element closest box found in the previous stage. If theselected element is not a box element, the algorithm matches theselected element with an end element within the matching element closestbox as described hereinbelow with reference to FIGS. 24D and 24E.

Turning to FIG. 24B, it is seen that once a matching box element isfound in the tree representation of the web page, the selected boxelement in the template is checked to see whether it includes anindication of added or removed content therein, or of use of an instanceof a basic structure repeated therein for adapting other instances ofthe repeated structure.

If the selected box element includes an indication that content shouldbe added, the required content is found in the template, and the contentis added following the node whose location is designated in thetemplate.

If the selected box element includes an indication that content shouldbe removed therefrom, the required content is found in the template, andthe content is removed from the location designated in the template.

As seen in FIG. 24C, if the selected box element includes an indicationof use of an instance of a basic structure repeated therein for adaptingother instances of the repeated structure, a repeated structure adaptingalgorithm, described hereinbelow with reference to FIGS. 28A-28E, isemployed.

As mentioned hereinabove with reference to FIG. 24A, if the selectedelement is not a box element, the algorithm matches the selected elementwith an end element within the matching element closest box.

As seen in FIG. 24A, in order to match end elements, full tree traversalmode is employed. Using an element path of the selected element relativeto its closest box element, a candidate matching element is locatedwithin the matching closest box element.

As seen in FIG. 24D, if, during the process of descending the sub treeof the matching closest box element in search of the candidate matchingelement, an element in the tree representation of the web page has fewerchildren than the respective number in the element path, the matchingalgorithm proceeds as described further hereinbelow.

As seen in FIG. 24D, if, during the process of descending the sub treeof the matching closest box element in search of the candidate matchingelement, no element in the tree representation of the web page has fewerchildren than the respective number in the element path, the candidatematching element is found, and the distance between the candidatematching element and the selected element is calculated using an endelement comparison algorithm, described hereinbelow with reference toFIGS. 27A and 27B. If the calculated distance is below a thirdpredetermined threshold, the matching element is found, and thealgorithm proceeds to match the next element.

If the calculated distance is above the third threshold, oralternatively, as described hereinabove, if during the process ofdescending the sub tree of the matching closest box element in search ofthe candidate matching element, an element in the tree representation ofthe web page has fewer children than the respective number in theelement path, the algorithm finds the minimum of the distances betweenthe selected end element and any element within the sub-tree of thematching closest element box having the same name as the selectedelement. The distances are calculated using the end element comparisonalgorithm, described hereinbelow with reference to FIGS. 27A and 27B.

As seen in FIG. 24E, if the minimum distance is below the thirdpredetermined threshold, the matching element is found, and thealgorithm proceeds to match the next element. If the minimum distance isnot below the third predetermined threshold, there is no matchingelement for the selected element. If the selected element is indicatedby the operator to be a mandatory element the matching algorithmterminates and the page is displayed in order without use of the VDTtemplate. If the selected element is not mandatory, the algorithmproceeds to process the next element.

Reference is now made to FIG. 25, which is a simplified flow chart of atree comparison algorithm used during operation of the matchingalgorithm of FIGS. 21-24E. In the tree comparison algorithm, a distanceis measured between a first root node of a first tree, hereinaftertermed node1, and a second root node of a second tree, hereinaftertermed node2. In general terms, the distance of a pair of trees iscalculated recursively, by calculating the distances of the sub-treesthereof, and combining the results, based on a weight function which maybe determined by the user or configured by the operator.

As seen in FIG. 25, the minimum of the number of child nodes of node1and the number of child nodes of node2 is found. Additionally, themaximum of the number of child nodes of node1 and the number of childnodes of node2 is found. Parameters representing the distance and thenumber of child nodes having different names in the two trees, referredto hereinbelow as ‘names parameter’, are initially set to 0.

For each of the child nodes of the parent nodes, such that the minimumnumber of child nodes is not exceeded, the name of the child node ofnode1 located at a given location is compared to the name of the childnode of node2 which is at the same location. If the names are not thesame, the names parameter is incremented by 1.

If the nodes have the same name, the distance parameter is incrementedby the distance of the two child nodes whose names were compared, suchthat the weight function is multiplied by a fraction, typically 0.95.

The distance between the two trees is then considered to be a functionof the distance and names parameters, the assigned weight, and themaximum and minimum numbers of child nodes calculated at the initialstages.

Reference is now made to FIGS. 26A, 26B and 26C, which together are asimplified flow chart of a box element comparison algorithm used duringoperation of the matching algorithm of FIGS. 21-24E. The box elementcomparison algorithm receives a pair of box elements, referred tohereinbelow as box1 and box2, and returns as a result a numberindicating the distance between the received elements. It will beappreciated that for the purpose of the matching algorithm describedhereinabove with reference to FIGS. 21-24E, box1 is considered to be thetemplate element, and box 2 is considered to be the web page element.

As seen in FIG. 26A, the elements names initially are compared. If theelements have different names, the algorithm return as a result a numberwhich is above the comparison threshold used hereinabove with referenceto FIGS. 21-24E.

If the element names are identical, the elements are checked to seewhether they include at least one of an image, a link, a form or a textelement. If one of the elements includes a sub-element of the listedtypes, and the other element includes no such sub-element, the algorithmreturns as a result a number which is above the comparison thresholdused hereinabove with reference to FIGS. 21-24E.

If both of the elements include at least one of an image, a link, a formor a text element, or if both of the elements do not include at leastone sub-element of the listed types, a distance parameter is defined andset to 0. If neither of box1 and box2 includes an indication that the Xlocation thereof should be ignored, the distance is incremented by theabsolute value of the difference between the X locations of box1 andbox2, divided by the X location of box1.

As seen in FIG. 26B, if neither of box1 and box2 includes an indicationthat the Y location thereof should be ignored, the distance isincremented by the absolute value of the difference between the Ylocations of box1 and box2, divided by the Y location of box1. It isappreciated that the X and Y locations of box1 and box2 are measuredrelative to the previous box element in the web page of which they formpart.

If neither of box1 and box2 includes an indication that the widththereof should be ignored, the distance is incremented by the absolutevalue of the difference between the widths of box1 and box2, divided bythe width of box1.

If neither of box1 and box2 includes an indication that the heightthereof should be ignored, the distance is incremented by the absolutevalue of the difference between the heights of box1 and box2, divided bythe height of box1.

The distance is then incremented by the absolute value of the differencebetween the number of images in box1 and box2, divided by the number ofimages in box1.

As seen in FIG. 26C, the distance is further incremented by the absolutevalue of the difference between the number of forms in box1 and box2,divided by the number of forms in box1. The distance is then incrementedby the absolute value of the difference between the percentage of areaof box1 covered by text and the percentage of area of box2 which iscovered by text, divided by the percentage of area of box1 which iscovered by text. The distance is further incremented by the absolutevalue of the difference between the percentage of area of box1 coveredby links and the percentage of area of box2 which is covered by links,divided by the percentage of area of box1 which is covered by links.

The algorithm returns as a result the distance parameter following allthe calculations described hereinabove.

Reference is now made to FIGS. 27A and 27B, which together are asimplified flow chart of an end element comparison algorithm employed inthe operation of the matching algorithm of FIGS. 21-24E. The end elementcomparison algorithm receives a pair of end elements, referred tohereinbelow as end1 and end2, and returns as a result a numberindicating the distance between the received elements. It will beappreciated that for the purpose of the matching algorithm describedhereinabove with reference to FIGS. 21-24E, end1 is considered to be thetemplate element, and end2 is considered to be the web page element.

As seen in FIG. 27A, the elements names initially are compared. If theelements have different names, the algorithm returns as a result anumber which is above the comparison threshold used hereinabove withreference to FIGS. 21-24E.

If the element names are identical, a distance parameter is defined andis set to 0. If neither of end1 and end2 includes an indication that theX location thereof should be ignored, the distance is incremented by theabsolute value of the difference between the X locations of end1 andend2, divided by the X location of end1.

If neither of end1 and end2 includes an indication that the Y locationthereof should be ignored, the distance is incremented by the absolutevalue of the difference between the Y locations of end1 and end2,divided by the Y location of end1. It is appreciated that the X and Ylocations of end1 and end2 are measured relative to the previous endelement in the web page of which they form part.

Turning to FIG. 27B, it is seen that if neither of end1 and end2includes an indication that the width thereof should be ignored, thedistance is incremented by the absolute value of the difference betweenthe widths of end1 and end2, divided by the width of end1.

If neither of end1 and end2 includes an indication that the heightthereof should be ignored, the distance is incremented by the absolutevalue of the difference between the heights of end1 and end2, divided bythe height of end 1.

The algorithm returns as a result the distance parameter following allthe calculations described hereinabove.

Reference is now made to FIGS. 28A, 28B, 28C, 28D and 28E which aretogether a simplified flow chart of a repeated structure adaptingalgorithm used during operation of the matching algorithm of FIGS.21-24E. The algorithm is applied to a box element which is indicated inthe template to contain a repeated structure. In order to employ therepeated structure adapting algorithm, the instance of the repeatedstructure for which adapting instructions are provided must be found.Once that instance is found, additional instances of the repeatedstructure, to which the adapting instructions are applied, are found.Once the adapting instructions are applied to the additional instances,the box element containing the repeated structure has been fullyadapted, and the next element may be matched.

As seen in FIG. 28A, boxed tree traversal mode is employed. The firstinstance of the repeated structure, for which adapting instructions areprovided, is found in the tree representation of the template, and theelement path thereof and is obtained. Information for the first instanceof the repeated structure is obtained from the template. The elementpath of the first instance of the repeated structure is followed in thetree representation of the web page.

If the information includes an indication that all the elementproperties, aside from its name and location in the tree, are to beignored, the following takes place.

As seen in FIG. 28B, if the element found in the tree representation ofthe web page, and the first instance of the repeated structure found inthe template have the same element name, the element found in the treerepresentation of the web page is considered to be the first instance ofthe repeated structure in the web page, and is adapted in accordancewith the adapting instructions found in the template. Otherwise, if theelements have different names, a candidate matching element is found ina similar manner to that described hereinabove with reference to FIGS.23A-23C, as described in more detail hereinbelow.

If the information does not include an indication that all the elementproperties, aside from its name and location in the tree, are to beignored, the following takes place: The distance between the elementfound in the tree representation of the web page and the first instanceof the repeated structure found in the template is calculated, using thebox element comparison algorithm described hereinabove with reference toFIGS. 26A-26C. Additionally, the structures of the sub-trees of theelements found in the tree representation of the web page and in thetree representation of the template are compared. If the distance isbelow a predetermined threshold, and the structures of the sub-trees ofthe elements are similar, the first instance of the repeated structurein the web page is found.

If the distance is above the threshold, or the structures of thesub-trees of the elements are not similar, or the elements havedifferent names, a candidate matching element is found in a similarmanner to that described hereinabove with reference to FIGS. 23A-23C.

As seen in FIG. 28C, once the first instance in the web page of therepeated structure is found, the algorithm proceeds to find additionalinstances of the repeated structure. All the elements in the treerepresentation of the web page which share the same immediate root nodeas the element representing the first instance of the repeated structure(sibling nodes of the element) are found.

If, as mentioned above, the first instance in the template tree of therepeated structure includes an indication that all the elementproperties, aside from its name and location in the tree, should beignored, the following takes place. As seen in FIG. 28D, for each of thecandidate repeated structure elements found, the name of the candidaterepeated structure is compared to that of the first instance of therepeated structure in the tree representation of the web page. If thename is not the same, the candidate repeated structure is not consideredto be an instance of the repeated structure.

Otherwise, if the name is the same, the structures of the sub-trees ofthe candidate repeated structure element and of the first instance ofthe repeated structure in the tree representation of the web page arecompared. If the structures of the sub-trees are not similar, thecandidate repeated structure is not considered to be an instance of therepeated structure. Otherwise, if the structures of the sub-trees aresimilar, the candidate repeated structure is considered to be aninstance of the repeated structure and is adapted in accordance with theadapting instructions found in the template.

As seen in FIG. 28E, if the first instance in the template tree of therepeated structure does not include an indication that all the elementproperties, aside from its name and location in the tree, should beignored, the following takes place. For each of the candidate repeatedstructure elements found, its distance from the first instance of therepeated structure in the tree representation of the web page iscalculated, using the box element comparison algorithm describedhereinabove with reference to FIGS. 26A-26C.

Additionally, the structures of the sub-trees of the candidate repeatedstructure element and of the first instance of the repeated structure inthe tree representation of the web page are compared. If the distance isbelow a predetermined threshold, and the structures of the sub-trees ofthe elements are similar, the candidate repeated structure is consideredto be an instance of the repeated structure and is adapted in accordancewith the adapting instructions found in the template. Otherwise, thecandidate repeated structure is not considered to be an instance of therepeated structure.

Reference is now made to FIGS. 29A, 29B, 29C and 29D, which illustratethe results of operation of a matching algorithm on a dynamic website,preferably, but not necessarily, within the context of the VDTfunctionality.

FIG. 29A shows a web page 350, including a logo region 352 and a loginregion 354. The web page 350 has a first general layout. As seen, anoperator employs the VDT functionality of FIGS. 11-18 to define atemplate suitable for display of an adapted web page 356, correspondingto web page 350, on a display screen 358 of a mobile communicator 360.As described hereinabove, the template is saved on a server 361, forfuture requests of the page 350.

Turning to FIG. 29B, it is seen that the adapted web page 356,corresponding to web page 350, is displayed on display screen 358 of themobile communicator 360. Based on the template defined by the operator,an adapted logo region 362, corresponding to logo region 352, and anadapted login region 364, corresponding to login region 354, areprovided on the mobile communicator 360.

As seen in FIG. 29A, the server 361 is preferably associated with adatabase 366, in which login information of users is maintained,typically in the form of cookies. If a cookie for a specific user orcomputer is saved in the database 366, when a user requests the same webpage again, the login information of the user is retrieved from thedatabase and a personalized web page 368 is provided, as shown in FIG.29C.

As seen in FIG. 29C, the personalized web page 368 includes a logoregion 370, a login status region 372, a website status region 374, anda personal information region 376, and typically has a very differentlayout than that of the initial web page 350. Due to the extremedifferences in the layout, preferably the operator defines a secondtemplate, suitable for display of an adapted personalized web page 378,corresponding to personalized web page 368, on the display screen 358 ofthe mobile communicator 360.

Turning to FIG. 29D, it is seen that the adapted personalized web page378, corresponding to personalized web page 368, is displayed on displayscreen 358 of the mobile communicator 360. Based on the second templatedefined by the operator, an adapted logo region 380, corresponding tologo region 370, an adapted login status region 382, corresponding tologin status region 372, an adapted website status region 384,corresponding to website status region 374, and an adapted personalinformation region 386, corresponding to personal information region376, are displayed on the mobile communicator 360.

It is appreciated that upon further requests of the web page, the server361 retrieves the web page from the Internet, and converts it into atree representation of the DOM. Subsequently, the web page is matched toa suitable template, in order to generate an adapted web page fordisplay on a mobile communicator. Typically, in order to find thesuitable template for a web page, the server finds all the templateshaving a scope including the requested web page. The distance betweenthe tree representation of the web page and the tree representations ofeach of the templates is calculated, using the tree comparison algorithmdescribed hereinabove with reference to FIG. 25. If the distance betweenthe tree representation of the web page and the tree representation of agiven template is below a predetermined threshold, that template is usedfor adapting the web page for display on a mobile communicator.

It is further appreciated that the tree comparison algorithm describedhereinabove with reference to FIG. 25 is suitable for determiningwhether any two tree representations of DOMs match each other.

In accordance with a preferred embodiment of the present invention,there is provided a method and system for obtaining information from atleast one dynamic website including:

constructing at least one template of at least a part of a web page ofthe at least one website when the web page is in a first state; and

employing the at least one template to extract information from at leastone web page of the at least one dynamic website when at least one ofthe at least one web page is in a second state, different from the firststate.

Typically, employing the at least one template to extract informationfrom at least one web page of the at least one dynamic website when atleast one of the at least one web page is in a second state, differentfrom the first state, includes effecting a best match between the atleast one template and document object models (DOMs) of the at least oneweb page in the second state.

In accordance with another preferred embodiment of the presentinvention, there is provided a method and system for obtaininginformation from at least one dynamic website including:

obtaining at least one document object model (DOM) of a web page of theat least one dynamic website when the web page is in a first state; and

employing the at least one document object model (DOM) to obtaininformation from at least one web page of the at least one dynamicwebsite when at least one of the at least one web page is in a secondstate, different from the first state.

Typically, employing the at least one document object model (DOM) toextract information from at least one web page of the at least onedynamic website when at least one of the at least one web page is in asecond state, different from the first state, includes effecting a bestmatch between the at least one document object model (DOM) and documentobject models (DOMs) of the at least one web page in the second state.

Reference is now made to FIG. 30A, which is a simplified pictorialillustration of functionality for reconstruction of fragmented imagesfor display on a mobile communicator in accordance with a preferredembodiment of the present invention and to FIGS. 30B and 30C, whichtogether are a simplified flow chart showing the operation of thefunctionality for reconstruction of fragmented images.

As seen in FIG. 30A, the functionality of the present invention isoperative to display an image forming part of a web page, such as image400 on web page 402, in the form of an adapted image 404 shown on anadapted web page 406, on a display screen 408 of a mobile communicator410, in a manner which is particularly suitable for viewing on displayscreen 408. It is a particular feature of the present invention that theadapted image 404 is displayed on the display screen 408 in its completeform, even if in the web page 402 it is formed of multiple sub-images,indicated by reference numeral 412.

It is seen that a conventional web page, such as web page 402, includesan image, such as image 400, which is formed of a plurality ofsub-images 412. It is a particular feature of the present invention thatwhen a user requests a web page, such as web page 402, the web page isdownloaded to a server 414, which is operative to recognize the presenceof an image 400 comprised of sub images 412. The server is furtheroperative to combine the sub images 412 into a single adapted image 404,and to supply the single adapted image 404 for display on the displayscreen 408.

Preferably, if one or more of the sub-images 412 includes non-imageinformation, that non-image information is preserved outside of thesingle adapted image 404 during the combining of the sub-images 412.

As seen in FIG. 30A, in the prior art, when a web page containing animage formed of multiple sub-images, such as image 400, is displayed ona display screen 420 of a mobile communicator 422, only the firstsub-image is displayed, as indicated by reference numeral 424.

Turning now to FIG. 30B, it is seen that a user initially requests a webpage, and the web page is downloaded to the server. The server thenconverts the web page into a modified tree representation of the DOM.

During the analysis of the page, described hereinabove with reference toFIG. 3, fragmented images are identified. For each fragmented image, theserver creates a file, typically an XML file, which includes informationrelated to each of the sub-images and to the whole image. Typically, thesource URL, top left corner, the width and the height of each sub-imageis written to the XML file, in addition to the width and heightdimensions of the composite image and its background color.

In the tree representation of the web page, all of the sub-images exceptfor the first sub-image, are flagged as being invisible. In the srcfield of the first sub-image, the source location is replaced by thelocation on the server of the XML file. Preferably, the width and heightof the first sub-image are ignored, in order to enable flexibility inadapting the composite image. An adapted web page, including thelocation on the server of the XML file, is returned to the user.

When the adapted web page is received by the mobile communicator, themobile communicator requests the image from the server. Due to thechange in the src field of the first sub image, when requesting theimage from the server the location of the XML file is provided to theserver, rather than the location of the sub-image.

As seen in FIG. 30C, the server retrieves the XML file corresponding tothe requested image. In the server, a memory area having the dimensionsof the composite image, as indicated in the XML file, is allocated, andthe background color of the allocated area is set to be the backgroundcolor of the image as defined in the XML file. Each of the sub-images isretrieved by using the URL indicated in the src field of its img tag,and is drawn in the allocated area in its appropriate location andhaving the appropriate dimensions, as indicated in the XML file.

If necessary, once the adapted image is assembled, it may be rescaled tofit the dimensions of the display screen of the mobile communicator fromwhich it was requested. The adapted image is then converted to the fileformat specified in the user request, and transmitted to the user.

Reference is now made to FIGS. 31 and 32A-32D which illustrate image mapfunctionality constructed and operative in accordance with a preferredembodiment of the present invention. The image map functionality of thepresent invention provides a method and system for displaying webcontent on a display screen including requesting a web page by a user;in response to a user request, downloading the web page to a server;recognizing, by the server, the presence in the web page of an image mapcontaining a plurality of links, corresponding to portions of the imagemap; dividing the image map into a plurality of sub-images correspondingto the portions of the image map; associating the plurality of linkswith corresponding ones of the plurality of sub-images; and supplyingthe plurality of sub-images for display on the display screen.

FIG. 31 is a simplified pictorial illustration of functionality fordisplaying web content on a mobile communicator in accordance with apreferred embodiment of the present invention, providing image mapfunctionality and FIGS. 32A, 32B, 32C and 32D illustrate examples ofdisplay screens of mobile communicators employing image mapfunctionality.

As seen in FIG. 31, the functionality of the present invention isoperative to display web content, such as a conventional web page 500having an image 502 and an associated image map on a display screen 506of a mobile communicator 508 in a manner which is particularly suitablefor viewing on display screen 506.

A server 510, requesting web page 500 from the Internet, detects thatthe image 502 has an image map associated therewith. The image mapprovides links associated with specific geographical areas forming partof the image 502, such as areas designated by reference numerals 512,514, 516 and 518.

The server 510 employs information in the image map to extract thegeographical areas of the image 502 and their corresponding links and toprepare the geographical areas for display as individual images ondisplay screen 506. This is typically achieved by employing informationindicating the spatial coordinates of each geographical areas of theimage 502 from the image map to copy that geographical area into a newimage with which is associated a unique link, corresponding to the linkdesignated by the image map.

As seen in FIG. 32A, a portion of an adapted web page 520 is displayedon display screen 506 of mobile communicator 508. By scrolling down, theindividual geographical areas of the image 502 are sequentiallydisplayed. The geographical areas corresponding to areas 512 and 514 arerespectively designated by reference numerals 522 and 524 in FIGS. 32B,32C and 32D.

Reference is now made to FIG. 33, which is a simplified flow chartillustrating the image map functionality of FIGS. 31-32D. As seen inFIG. 33, a user initially requests a web page, and the web page isdownloaded to the server. The server then converts the web page into amodified tree representation of the DOM.

During the analysis of the page, described hereinabove with reference toFIG. 3, <map> tags, indicating the presence of image maps, are located.For each <map> tag found, the image associated therewith is located.

In the adapted web page being created, a set of image links,representing each of the geographical areas of the image map, is createdimmediately following the image. Typically, each of the image linkscorresponds to a given geographical area of the image map. Each imagelink includes as its src field the URL of the original image, such asimage 502 (FIGS. 31-32D), information indicating the borders of thegeographical area to which the link corresponds, and additionalinformation required for displaying an image on a display screen of amobile communicator, such as display screen 506 of mobile communicator508 (FIGS. 31-32D). An adapted web page, including the added set oflinks, is returned to the user.

When the adapted web page is received by the mobile communicator, themobile communicator requests the image links from the server. The serverthen retrieves the image from the Internet, crops the image inaccordance with the parameters provided in the link, and transmits theadapted link to the user.

It will be appreciated that the link transmitted to the user, which isdisplayed beneath the image, corresponds in all manners to the linkdefined as part of the image map in the given geographical area, andprovides a link to the same web page.

Reference is now made to FIG. 34, which illustrates interactivecommunication between a conventional interactive web page 700 having aclient-side script, such as JavaScript, and a mobile device, such as amobile communicator 701 via a server 702 which provides client-sidescript emulation in accordance with a preferred embodiment of thepresent invention. It is seen that the web page 700 includes a radiobutton selection region 703 which here includes two radio buttons 704and 706, respectively indicated as “one-way” or “return”. Below theradio button selection region 703 is an event triggering select region708 and an event triggered select region 710. The event triggeringselect region 708 here includes a number of clickable departurelocations and the event triggered select region 710 here includes anumber of clickable destination locations. It is appreciated that thedestination locations appearing in region 710 are determined by theselected departure location.

Below regions 708 and 710 there is typically found a departure dateselection location 712 which enables a user to enter a desired departuredate. When the “return” radio button 706 is selected, a return dateselection location 714 is activated. Various other selection regions arealso present on web page 700.

Reference is now made to FIGS. 35A-35C, which together are a simplifiedflow chart illustrating operation of client-side script emulation inaccordance with a preferred embodiment of the present invention, and toFIGS. 36A-36G, which illustrate a display screen 718 of a mobile device720, such as a Nokia 6630, illustrating the results of this emulation.

Turning to FIG. 35A, it is seen that a user requests an HTML web pagefrom server 702, which retrieves the requested web page from theinternet and searches the web page for elements that contain eventattributes such as “onevent” and thus require client-side scriptemulation. If no such elements are found, a mobile communicator adaptedweb page corresponding to the web page 700 is supplied by server 702 tothe mobile communicator 701.

If at least one element that requires client-side script emulation isfound, the following takes place on the mobile communicator adapted webpage corresponding to the web page 700:

I. Each element, such as radio buttons 704 and 706, respectivelyindicated as “one-way” or “return”, is replaced by an input tag of asubmit type (<input type=submit . . . >) having a unique name. Thevisual appearance of the input tag of a submit type preferably is set tobe similar to the visual appearance of the original element. Preferably,if the mobile communicator supports use of an input tag of an imagetype, an input tag of an image type is used instead of the input tag ofa submit type. The visual appearance of the input tag of an image typetypically is set to be similar to the visual appearance of the originalelement.

II. If an element is not within an HTML form tag, an HTML anchor tag iscreated around the element.

Turning to FIG. 35B, the process continues as follows:

III. A look-up table is created for the requested web page and indexedby the unique names of the input tags of the submit type. The tablecontains information such as a name of the element to which each inputtag corresponds, an ID attribute of the element, the type of the elementand the location of the element in the DOM of the web page 700.Alternatively, the look-up table may be replaced by any other suitablekey-accessed information storage medium.

IV. An input tag of a “hidden” type is added to the HTML form defined byan HTML form tag referenced in II and III above. The value of this inputtag is employed to identify the look-up table.

V. If the element is a select element, corresponding to a select region,such as region 708 or 710 (FIG. 34), a plurality of option-displayingadapted pages, each containing a limited number of options, such as ten,are prepared. Each of the available options in the select region appearson one of the adapted option-displaying pages. Each of the availableoptions is a link to server 702 and contains a value which is employedto identify the look-up table. If the options are arranged in apredetermined order, such as an alphabetical order, an adapted pagecontaining a listing thereof is preferably prepared.

The adapted web page, downstream of steps I-V, is supplied to the mobilecommunicator 701, as web page 730, seen in FIG. 36A. It is a particularfeature of the present invention that the buttons 734 and 736 whichappear identical to radio buttons 704 and 706 in web page 700 (FIG. 34),have submit button functionality. Similarly, in FIG. 36B, whichillustrates a scrolled down view of web page 730, select regions 738 and740, which appear similar or identical to select regions 708 and 710(FIG. 34) also have submit button functionality.

Typically, when a user clicks on an element that is a select region,such as select region 738 (FIG. 36B), the corresponding HTML form issubmitted to server 702 (FIG. 34). The server 702, upon receipt of theHTML form submission, recognizes the HTML form submission as a requestto display the general listing of options 742 (FIG. 36C), if available.

As seen in FIG. 35C, if there is no general listing of options, a firstadapted option-displaying page is shown. Alternatively, if the generallisting of options is displayed, the user may select a specific adaptedoptions displaying page 744 (FIG. 36D).

The user then selects an option. This selection operates as a HTTPrequest to the server 702. The server 702 identifies this request as anemulation request. The server 702 finds the unique name of the input tagof the submit type and the look up table and thus finds information toenable it to identify a corresponding option element on the DOM. Theoption element is found in the following manner: The server 702 againrequests the web page 700 from the Internet and creates a DOMcorresponding to the web page. The information found on the look-uptable is employed to locate the option element on the DOM and the eventattributes thereof.

An event identified by the event attributes of the element is triggeredby the server 702, resulting in emulation of a user operating aconventional web browser, producing an adapted page 750, such as thatshown in FIG. 36E. The information found on the lookup table is saved inan emulation list associated with the look-up table so that retrievingthe look-up table also retrieves the emulation list. Alternatively, theinformation may be stored in any suitable storage medium.

Returning to FIG. 35B, it is seen that when a user selects an element,such as one of radio buttons 734 and 736, that has submit buttonfunctionality, but is not a select region, this selection operates as aHTTP request to the server 702. The server 702 identifies this requestas an emulation request. As seen in FIG. 35C, the server 702 finds theunique name of the input tag of the submit type and the look up tableand thus finds information to enable it to identify the element selectedby the user. The user-selected element is found in the following manner:The server 702 again requests the web page 700 from the Internet andcreates a DOM corresponding to the web page. The information found onthe look-up table is employed to locate the element on the DOM.

An event identified by the event attributes of the user-selected elementis triggered by the server 702, resulting in emulation of a useroperating a conventional web browser, producing an adapted page 760,such as that shown in FIG. 36F. The information found on the lookuptable is saved in an emulation list associated with the look-up table sothat retrieving the look-up table also retrieves the emulation list.Alternatively, the information may be stored in any suitable storagemedium.

If on an adapted page 750 or 760, the user selects a further elementthat has submit button functionality, then the selection operates as aHTTP request to the server 702. The server 702 identifies this requestas an emulation request. The server 702 finds the unique name of theinput tag of the submit type and the look up table and the emulationlist. The emulation list contains the information of the previousemulations. The server 702 requests the web page 700 from the Internetand creates a DOM corresponding to the web page. The information of allthe previous emulations in the emulation list is used to trigger theemulations in the order of their occurrence. The look-up table enablesthe server 702 to identify the further user-selected element. Thelook-up table enables the server 702 to identify the furtheruser-selected element on the DOM.

An event identified by the event attributes of the user-selected elementis triggered by the server 702, resulting in emulation of a useroperating a conventional web browser, producing an adapted page 770,such as that shown in FIG. 36G. The information found on the lookuptable is saved in an emulation list associated with the look-up table sothat retrieving the look-up table also retrieves the emulation list.Alternatively, the information may be stored in any suitable storagemedium.

Reference is now made to FIGS. 37A and 37B, which together aresimplified illustrations of the structure and operation of functionalityfor automatic configuration of a database used to adapt web content foruse with mobile communicators, constructed and operative in accordancewith a preferred embodiment of the present invention, and to FIGS. 38Aand 38B, which together are a simplified flow chart of operation of thefunctionality for automatic configuration of FIGS. 37A and 37B.

As seen in FIG. 37A, the functionality of the present invention isoperative to display web content, associated with a web page 800, on adisplay screens of mobile communicators 802 and 804, having differingproperties by employing the following general steps:

receiving an http request 810 from one of the mobile communicators,typically mobile communicator 802;

retrieving at least one device identifying field 812, such as auser-agent field or pattern in the http request 810, which field 812identifies the mobile communicator 802;

searching in a device identification database 814 for device propertiesinformation 816 associated with the field 812;

if the searching is successful, adapting web page 800 corresponding tothe http request 810 in accordance with the device propertiesinformation 816; and

transmitting the adapted web page 818 corresponding to the http request810 to the mobile communicator 802.

As illustrated in FIG. 37A, the user employs mobile communicator 802 torequest a web page. The http request 810 is provided to a server 819, asindicated by arrow A. The server 819 is operative to retrieve from theheaders of the http request 812, at least one device identifying field812, such as a user-agent pattern or regular expression thereof. As seenat arrow B, the device identifying field 812 is employed as a key inaccessing a device identification database 814, which is typicallyassociated with the server 819, in order to retrieve device propertiesinformation 816 therefrom.

The database 814 is preferably a hierarchical database. Typically, theprocess of matching the device identifying field 812 to the deviceproperties information 816 in the database 814 begins at a root of thefamily of devices within the database 814, and continues down thedatabase hierarchy to subsequent levels, until the exact device,identified by the device identifying field 812, is found, and deviceproperties information 816 therefor are retrieved. The device propertiesinformation 816 found in the database 814 is transmitted to the server819 as indicated by arrow C.

Subsequently or in parallel, the server 819 requests the web pagecorresponding to the http request 810 as indicated by arrow D, anddownloads the corresponding web page, such as web page 800, from theInternet, as indicated by arrow E.

At the server 819, the web page 800 is adapted in accordance with thedevice properties information 816, and the adapted web page 818,corresponding to the http request 810, is transmitted to the user, asindicated by arrow F.

Turning now to FIG. 37B, it is seen that in another case, involvinganother mobile communicator, such as mobile communicator 804, whichsends an http request 820 corresponding to a web page 821, the followinggeneral steps take place:

retrieving at least one device identifying field 822, such as auser-agent pattern in the http request 820, which field 822 identifiesthe mobile communicator 804;

searching in the device identification database 814 for deviceproperties information associated with the field 822;

if the searching is not successful, as in this case, conducting at leasta search of at least one external database 830 to obtain deviceproperties information 836 regarding the mobile communicator 804;

employing information received from the search of database 830 to updatethe device identification database 814 with properties of the mobilecommunicator 804 identified by the device identifying field 822 andadapting the web page 821 corresponding to the http request 820 inaccordance with the device properties information 836 obtained by thesearch of external database 830; and

transmitting the adapted web page 838 corresponding to the http request820 to the mobile communicator 804.

As illustrated in FIG. 37B, the user employs mobile communicator 804 torequest a web page 821. The http request 820 is provided to a server819, as indicated by arrow A. The server 819 is operative to retrievefrom the headers of the http request 820, at least one deviceidentifying field 822, such as a user-agent pattern or regularexpression thereof. As seen at arrow B, the device identifying field 822is employed as a key in accessing a device identification database 814,which is typically associated with the server 819, in order to retrievetherefrom device properties information associated with the device 804.

As seen at arrow C, some or all of the device properties information forthe device identified by the device identifying field 822 is not foundin database 814. Typically, for each device or device family, thedatabase includes an indication whether auto-configuration of the devicefamily should be carried out if properties are missing. If, in thedatabase 814, the device family of the device 804 identified by thedevice identifying field 822 includes an indication thatauto-configuration should be carried out, this indication is provided tothe server 819.

Subsequently, the server 819 employs the device identifying field 822,and possibly additional device identifiers, such as information providedin an accept header of the http request 820, as keys in accessing atleast one external database 830, to search for properties of the devicetherein. Typically, as seen at arrow D, the external databases 830 maybe prioritized, such that a search is initially carried out in oneexternal database, and if not all the required information is foundtherein, a subsequent search is carried out in additional externaldatabases. Examples of external databases which may be used forauto-configuration are a UAProf provided by the device manufacturer, anda WURFL database, which is accessible throughhttp://wurfl.sourceforge.net/index.php.

As seen in FIG. 37B, some of the device properties information is foundin a first external database, indicated by reference numeral 832, and isreturned to the server 819, as indicated at arrow E. The remainingrequired device properties information is found in a second externaldatabase, indicated by reference numeral 834, and is returned to theserver as indicated at arrow F.

As seen at arrow G, the device properties information collected from theexternal databases 830 is combined into complete device propertiesinformation 836, which is automatically added by server 819 to database814. Typically, the device properties information includes defaultinformation retrieved from database 814, and additional informationobtained from external databases 830.

Preferably, an operator of database 814 may update, change, accept orreject device properties information which was automatically added todatabase 814.

Subsequently or in parallel, the server 819 requests the web pagecorresponding to the http request 820 as indicated by arrow H, anddownloads the corresponding web page 821 from the Internet, as indicatedby arrow I.

At the server 819, the web page 821 is adapted in accordance with thedevice properties information 836, and the adapted web page 838,corresponding to the http request 820, is transmitted to the user, asindicated by arrow J.

As seen with particular clarity in FIGS. 38A and 38B, it is appreciatedthat if the device properties information for the device identified bythe device indicating field 822 is not found in any of the externaldatabases 830, or alternatively if the device family in database 814does not include an auto-configuration indication, the data provided inthe accept header of the http request 820 and additional default datafor the device family is used as device properties information, and theweb page 821 is adapted accordingly.

A CD-ROM Appendix is enclosed herewith from which can be derived fileswhich, taken together, provide functionalities in accordance with thepreferred embodiment of the present invention.

In order to generate a system implementing functionalities describedhereinabove, based on the CD-ROM appendix, the following method may beemployed:

1. Provide an Intel compatible computer with having the followinghardware properties:

-   -   a. Two Dual Core Intel® Xeon® 5160 processors (3.0 GHz, 1333 MHz        FSB), 4 MB L2 Cache (Xeon 5100).    -   b. 2 GB 667 MHz, Ranked DIMMs    -   c. Two NC7781 PCI-X Gigabit NICs 10/100/1000 WOL    -   d. RAID 1 setting    -   e. 2×36 GB Pluggable Ultra320 SCSI 15,000 rpm Universal Hard        Drive    -   f. 24× Low-profile IDE CD-ROM Drive    -   g. Two 1″ Ultra 320 SCSI Hot Plug Drive Bays    -   h. Redundant Hot Plug Power Supplies    -   i. Redundant Hot Plug Fans

2. On the Intel compatible computer, provide the following software:

-   -   a. Microsoft Windows 2003 R2 standard Edition    -   b. Microsoft Internet Information Services 6.0    -   c. Microsoft Internet Security and Acceleration 2004 with        service pack 2    -   d. Microsoft Core XML Services 6 (MSXML)    -   e. Microsoft Internet Explorer 6

3. Provide an always-open Internet connection

4. Make sure the computer has two hard drive partitions labeled ‘C’ and‘D’ with at least 500 MB free space on the ‘D’ partition.

5. Log into the server as the Administrator

6. Copy the file setupexe.hex located in folder \apndx-I\ stored in theappended CD-ROM into a temporary directory.

7. Unhex the computer listing setupexe.hex mentioned in step 6 using HEXIT V1.8 or greater by John Augustine, 3129 Earl St., Laureldale, Pa.19605, USA creating file setup.exe

8. rename the file setup.exe mentioned in step 7 to “infogin setup.exe”

9. Copy the file proxyexe.hex located in folder \apndx-I\ stored in theappended CD-ROM into a temporary directory.

10. Unhex the computer listing proxyexe.hex mentioned in step 9 usingHEX IT V1.8 or greater by John Augustine creating file “proxy.exe”

11. Copy the file setupini.hex located in folder \apndx-I\ stored in theappended CD-ROM into a temporary directory.

12. Unhex the computer listing setupini.hex mentioned in step 11 usingHEX IT V1.8 or greater by John Augustine creating file “setup.ini”

13. Edit the ‘Setup.ini’ file by replacing the placeholder ‘IPADDRESS’with the IP address of the server

14. Run the file ‘Infogin Setup.exe’

15. Agree to the license

16. Specify the location of the ‘Setup.ini’ file

17. At the end of the installation, an Internet Explorer window willopen to the macromedia flash update page—follow the instructions on theweb page to make sure the server is installed with the latest version

18. Click OK after verifying the update of the flash version

19. Click Finish.

It will be appreciated by persons skilled in the art that the presentinvention is not limited by what has been particularly shown anddescribed hereinabove. Rather the scope of the present inventionincludes combinations and subcombinations of various features of thepresent invention as well as modifications which would occur to personsreading the foregoing description and which are not in the prior art.

The invention claimed is:
 1. A method for interactive communication witha web site using a mobile communicator that does not support aclient-side script employed by said web site, the method comprising:receiving, at a server, an hypertext transfer protocol (http) requestfrom said mobile communicator being used by a user, said http requestidentifying said website; and causing said server to emulate saidclient-side script by running said client-side script entirely on saidserver thereby enabling said user to interact with said website; saidenabling said user to interact comprising: receiving at least one userinput from said mobile communicator; and based on said at least one userinput, emulating at least one additional client-side script by runningsaid at least one additional client-side script entirely on said server;and wherein, when a user requests an Hyper Text Markup Language (HTML)web page from said server, said server retrieves the HTML web pagerequested from the internet and searches the HTML web page for elementsthat require client-side script emulation, and when at least one elementthat requires client-side script emulation is found, the following takesplace on a mobile communicator adapted web page corresponding to saidHTML web page requested by said user: each element respectivelyindicated as “one-way” or “return” is replaced by an input tag of asubmit type (<input type=submit . . . >) having a unique name unless themobile communicator supports use of an input tag of an image type, inwhich case an input tag of an image type is employed instead of theinput tag of a submit type.
 2. A method for interactive communicationwith a web site using a mobile communicator according to claim 1 andalso comprising: retrieving a user-agent field from said http request,said user-agent field identifying said mobile communicator being used bysaid user; and ascertaining whether said mobile communicator being usedby said user supports a given computer language or script.
 3. A methodfor interactive communication with a web site using a mobilecommunicator according to claim 1 and also comprising: employing aconventional browser of the mobile communicator for communicating withsaid server.
 4. A method for interactive communication with a web siteusing a mobile communicator according to claim 1 and also comprising:employing a form submit button to replace script elements not supportedby said mobile communicator.
 5. A method for interactive communicationwith a web site using a mobile communicator according to claim 4 andwherein said form submit button appears as a picture which resemblessaid script element.
 6. A method for interactive communication with aweb site using a mobile communicator according to claim 1 and whereinsaid client-side script is JavaScript and said server providesclient-side emulation of said JavaScript.
 7. A method for interactivecommunication with a web site using a mobile communicator according toclaim 1 and wherein visual appearance of said input tag of a submit typeis set to be similar to a visual appearance of an element to which itcorresponds.
 8. A method for interactive communication with a web siteusing a mobile communicator according to claim 1 and wherein: if saidelement is within an HTML form tag having an action attribute, a valueof the action attribute of the HTML form tag is replaced by an InternetProtocol (IP) address of said server; and if said element is not withinan HTML form tag, an HTML form tag is created around said element andthe action attribute of the HTML form tag is set to be the IP address ofsaid server.
 9. A method for interactive communication with a web siteusing a mobile communicator according to claim 1 and wherein: a look-uptable is created for the HTML web page requested; and said look-up tableis indexed by the unique names of the input tags of the submit type. 10.A method for interactive communication with a web site using a mobilecommunicator according to claim 9 and wherein said look-up tablecontains information including at least one of the following items: aname of said element to which each input tag corresponds; an IDattribute of said element; a type characterizing said element; andlocation of the element in the Document Object Model (DOM) of said HTMLweb page.
 11. A method for interactive communication with a web siteusing a mobile communicator according to claim 10 and wherein an inputtag of a “hidden” type is added to an HTML form defined by said HTMLform tag and the value of said input tag is employed to identify thelook-up table.
 12. A method for interactive communication with a website using a mobile communicator according to claim 11 and wherein ifsaid element is a select element, corresponding to a select region, aplurality of option-displaying adapted pages, each containing a limitednumber of available options, are prepared, each of said availableoptions in said select region appearing on one of the option-displayingadapted pages, each of the available options being a link to said serverand containing a value which is employed to identify the look-up table.13. A method for interactive communication with a web site using amobile communicator according to claim 12 and wherein when a user clickson a select region, a corresponding HTML form is submitted to saidserver which, upon receipt of the HTML form submitted, recognizes theHTML form submitted as a request to display either a general listing ofoptions, if available, or to display a first adapted option-displayingpage.
 14. A method for interactive communication with a web site using amobile communicator according to claim 13 and wherein a user selectionof an option operates as a HTTP request to said server, which identifiessaid HTTP request as an emulation request and finds said unique name ofsaid input tag of the submit type and said look up table and identifiesa corresponding option element on the DOM based on said unique name andsaid look-up table.
 15. A method for interactive communication with aweb site using a mobile communicator according to claim 14 and whereinsaid corresponding option element is found in the following manner: saidserver again requests said HTML web page from the internet and creates aDOM corresponding to said HTML web page and said information found onsaid look-up table is employed to locate the corresponding optionelement on the DOM.
 16. A method for interactive communication with aweb site using a mobile communicator according to claim 15 and whereinan event identified by event attributes of said corresponding optionelement is triggered by said server, resulting in emulation of a useroperating a conventional web browser, producing an adapted page, andsaid information found on said lookup table is saved in an emulationlist associated with the look-up table so that retrieving the look-uptable also retrieves the emulation list.
 17. A method for interactivecommunication with a web site using a mobile communicator according toclaim 1 and wherein when a user selects an element that has submitbutton functionality, but is not a select region, an HTTP request issubmitted to said server and the server identifies the HTTP request asan emulation request, finds the unique name of the input tag of thesubmit type and the look up table, and identifies the element that hassubmit button functionality selected by the user.
 18. A method forinteractive communication with a web site using a mobile communicatoraccording to claim 17 and wherein said element that has submit buttonfunctionality is found in the following manner: said server againrequests said HTML web page from the Internet and creates a DOMcorresponding to the HTML web page and said information found on thelook-up table is employed to locate the element on the DOM.
 19. A systemfor interactive communication with a web site using a mobilecommunicator that does not support a client-side script employed by saidweb site, the system comprising: a server operative to: receive anhypertext transfer protocol (http) request from said a mobilecommunicator being used by a user, said http request identifying saidwebsite; and emulate said client-side script by running said client-sidescript entirely on said server so as to enable user interaction withsaid website, said user interaction comprising: receiving, at saidserver, at least one user input from said mobile communicator; and basedon said at least one user input, emulating at least one additionalclient-side script by running said at least one additional client-sidescript entirely on said server; and wherein, when a user requests anHyper Text Markup Language (HTML) web page from said server, said serverretrieves the HTML web page requested from the internet and searches theHTML web page for elements that require client-side script emulation,and when at least one element that requires client-side script emulationis found, the following takes place on a mobile communicator adapted webpage corresponding to said HTML web page requested by said user: eachelement respectively indicated as “one-way” or “return” is replaced byan input tag of a submit type (<input type=submit . . . >) having aunique name unless the mobile communicator supports use of an input tagof an image type, in which case an input tag of an image type isemployed instead of the input tag of a submit type.
 20. A system forinteractive communication with a web site using a mobile communicatoraccording to claim 19 and wherein said functionalities also comprise:retrieving a user-agent field from said http request, said user-agentfield identifying said mobile communicator being used by said user; andascertaining whether said mobile communicator being used by said usersupports a given computer language or script.
 21. A system forinteractive communication with a web site using a mobile communicatoraccording to claim 19 and wherein said functionalities also comprise:employing a conventional browser of the mobile communicator forcommunicating with said server.
 22. A system for interactivecommunication with a web site using a mobile communicator according toclaim 19 and wherein said functionalities also comprise: employing aform submit button to replace script elements not supported by saidmobile communicator.
 23. A system for interactive communication with aweb site using a mobile communicator according to claim 22 and whereinsaid form submit button appears as a picture which resembles said scriptelement.
 24. A system for interactive communication with a web siteusing a mobile communicator according to claim 19 and wherein saidclient-side script is JavaScript and said server provides client-sideemulation of said JavaScript.
 25. A system for interactive communicationwith a web site using a mobile communicator according to claim 19 andwherein visual appearance of said input tag of a submit type is set tobe similar to a visual appearance of an element to which it corresponds.26. A system for interactive communication with a web site using amobile communicator according to claim 19 and wherein: if said elementis within an HTML form tag having an action attribute, a value of theaction attribute of the HTML form tag is replaced by an InternetProtocol (IP) address of said server; and if said element is not withinan HTML form tag, an HTML form tag is created around said element andthe action attribute of the HTML form tag is set to be the IP address ofsaid server.
 27. A system for interactive communication with a web siteusing a mobile communicator according to claim 19 and wherein: a look-uptable is created for the HTML web page requested; and said look-up tableis indexed by the unique names of the input tags of the submit type. 28.A system for interactive communication with a web site using a mobilecommunicator according to claim 27 and wherein said look-up tablecontains information including at least one of the following items: aname of said element to which each input tag corresponds; an IDattribute of said element; a type characterizing said element; andlocation of the element in the Document Object Model (DOM) of said HTMLweb page.
 29. A system for interactive communication with a web siteusing a mobile communicator according to claim 28 and wherein an inputtag of a “hidden” type is added to an HTML form defined by said HTMLform tag and the value of said input tag is employed to identify thelook-up table.
 30. A system for interactive communication with a website using a mobile communicator according to claim 29 and wherein ifsaid element is a select element, corresponding to a select region, aplurality of option-displaying adapted pages, each containing a limitednumber of available options are prepared, each of said available optionsin said select region appearing on one of the option-displaying adaptedpages, each of the available options being a link to said server andcontaining a value which is employed to identify the look-up table. 31.A system for interactive communication with a web site using a mobilecommunicator according to claim 30 and wherein when a user clicks on aselect region, a corresponding HTML form is submitted to said serverwhich, upon receipt of the HTML form submitted, recognizes the HTML formsubmitted as a request to display either a general listing of options,if available, or to display a first adapted option-displaying page. 32.A system for interactive communication with a web site using a mobilecommunicator according to claim 31 and wherein a user selection of anoption operates as a HTTP request to said server, which identifies saidHTTP request as an emulation request and finds said unique name of saidinput tag of the submit type and said look up table and identifies acorresponding option element on the DOM based on said unique name andsaid look-up table.
 33. A system for interactive communication with aweb site using a mobile communicator according to claim 32 and whereinsaid corresponding option element is found in the following manner: saidserver again requests said HTML web page from the internet and creates aDOM corresponding to said HTML web page and said information found onsaid look-up table is employed to locate the corresponding optionelement on the DOM.
 34. A system for interactive communication with aweb site using a mobile communicator according to claim 33 and whereinan event identified by event attributes of said corresponding optionelement is triggered by said server, resulting in emulation of a useroperating a conventional web browser, producing an adapted page, andsaid information found on said lookup table is saved in an emulationlist associated with the look-up table so that retrieving the look-uptable also retrieves the emulation list.